- 1. send to self patch (score: 1)
- Author: rald Welte <laforge@xxxxxxxxxxxx>
- Date: Mon, 22 Nov 2004 15:55:53 +1100
- ng
- /archives/netdev/2004-11/msg00784.html (6,834 bytes)
- 2. send to self patch (score: 1)
- Author: avid S. Miller" <davem@xxxxxxxxxx>
- Date: Fri, 29 Aug 2003 03:48:59 +1000
- is breaks upward compatibility ? i.e. this now assumes that for insta
- /archives/netdev/2003-08/msg00872.html (14,580 bytes)
- 3. Re: send to self patch (score: 1)
- Author:
- Date: Thu, 28 Aug 2003 14:22:47 -0500
- but sometimes thats not enough. eg When running netperf, you dont al
- /archives/netdev/2003-08/msg00873.html (18,582 bytes)
- 4. send to self patch (score: 1)
- Author: Anton Blanchard <anton@xxxxxxxxx>
- Date: Mon, 22 Nov 2004 15:55:53 +1100
- Hi, We've been using Julian Anastasov's send to self patch quite a lot. It has been useful for a number of things including POWER5 system test (where we stress a single system with a number of networ
- /archives/netdev/2004-11/msg01838.html (6,849 bytes)
- 5. send to self patch (score: 1)
- Author: Anton Blanchard <anton@xxxxxxxxx>
- Date: Fri, 29 Aug 2003 03:48:59 +1000
- Hi, Here in the lab we often want to send TCP/IP data out over looped back networks. We do have tools to send and receive raw packets but sometimes thats not enough. eg When running netperf, you dont
- /archives/netdev/2003-08/msg01844.html (14,595 bytes)
- 6. Re: send to self patch (score: 1)
- Author: "James R. Leu" <jleu@xxxxxxxxxxxxxx>
- Date: Thu, 28 Aug 2003 14:22:47 -0500
- While the various 'send-to-self' patches are useful for exactly what you are trying to do, I think a more generic solution, which has as one of it's features the ability to 'send-to-self', should be
- /archives/netdev/2003-08/msg01845.html (18,769 bytes)
This search system is powered by
Namazu