Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*network\s+delay\s+simulation\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*network\s+delay\s+simulation\s*$/: 24 ]

Total 24 documents matching your query.

1. network delay simulation (score: 1): Author: garzik@xxxxxxxxx>; Date: Tue, 16 Mar 2004 15:10:58 -0800; Still bumming around for how to easily simulate long latencies. There is NISTnet but that is fugly old 2.2 code; and Dummynet, and hitbox which are FreeBSD based. The existing traffic shaper might do; /archives/netdev/2004-03/msg00317.html (8,385 bytes)
2. Re: network delay simulation (score: 1): Author: mminger@xxxxxxxx>; Date: Wed, 17 Mar 2004 00:00:48 +0100; iirc there was a 2.4 port of NistNet. Porting it to 2.6 is probably not that much work. -Andi; /archives/netdev/2004-03/msg00318.html (8,850 bytes)
3. Re: network delay simulation (score: 1): Author: leen <ak@xxxxxxx>; Date: Tue, 16 Mar 2004 17:41:34 -0800; Probably a packet scheduler would be my first choice, you could then even tag packets using classification and therefore delay differently for different flows. Another thing I've always wanted to do; /archives/netdev/2004-03/msg00319.html (9,611 bytes)
4. Re: network delay simulation (score: 1): Author: davem@xxxxxxxxxx>; Date: Tue, 16 Mar 2004 17:50:52 -0800; nistnet works, but even akpm remembers it as pretty grotty, who knows maybe the most recent 2.4.x variant was much better, but I doubt it.; /archives/netdev/2004-03/msg00320.html (8,678 bytes)
5. Re: network delay simulation (score: 1): Author: davem@xxxxxxxxxx>; Date: Wed, 17 Mar 2004 03:06:34 +0100; For testing it's probably good enough. No need to merge it ;-) -Andi; /archives/netdev/2004-03/msg00321.html (9,152 bytes)
6. Re: network delay simulation (score: 1): Author: leen <ak@xxxxxxx>; Date: Tue, 16 Mar 2004 18:40:01 -0800; Stephen Hemminger wrote: Still bumming around for how to easily simulate long latencies. There is NISTnet but that is fugly old 2.2 code; and Dummynet, and hitbox which are FreeBSD based. The existin; /archives/netdev/2004-03/msg00322.html (9,913 bytes)
7. Re: network delay simulation (score: 1): Author: leen <ak@xxxxxxx>; Date: Wed, 17 Mar 2004 10:37:59 -0500 (EST); One insight I had a while ago is that packet pacing and artificial delay require a very similar mechanism. I hacked something a while ago that did this in a general way, though it had some problems a; /archives/netdev/2004-03/msg00336.html (9,548 bytes)
8. Re: network delay simulation (score: 1): Author: jheffner@xxxxxxx>; Date: 17 Mar 2004 11:09:26 -0500; I had something trying to replace nistnet a while back - probably have to go 10 harddrives back to find it. This is exactly what i had. You need to be able to choose what flow gets affected and which; /archives/netdev/2004-03/msg00337.html (11,063 bytes)
9. Re: network delay simulation (score: 1): Author: a <khc@xxxxxxxxx>; Date: Wed, 17 Mar 2004 09:51:07 -0800; Yes, but you want to weight it just a bit. Userland could use random() to generate the bit-stream in fact :); /archives/netdev/2004-03/msg00339.html (9,436 bytes)
10. Re: network delay simulation (score: 1): Author: davem@xxxxxxxxxx>; Date: Wed, 17 Mar 2004 10:00:01 -0800; In an earlier project we had a test suite that failed the Nth allocation, then repeated startup failing from 1 till all allocations in a typical interaction round trip had been tested. Sure led to so; /archives/netdev/2004-03/msg00340.html (10,427 bytes)
11. Re: network delay simulation (score: 1): Author: mminger@xxxxxxxx>; Date: Wed, 17 Mar 2004 10:25:15 -0800; Yes, but we don't really want alloc_skb() doing this, this makes the failures go to other places (like TCP, netlink, whatever) instead of what you're trying to actually test (RX out of buffer handlin; /archives/netdev/2004-03/msg00341.html (10,249 bytes)
12. Re: network delay simulation (score: 1): Author: garzik@xxxxxxxxx>; Date: Wed, 17 Mar 2004 19:17:16 -0800; whaddya mean "even"? I wrote a userspace thingy many moons ago which provides variable delays and bandwidth restriction. It's for simulating long, thin pipes. It uses the tap/tun interface to route p; /archives/netdev/2004-03/msg00347.html (9,807 bytes)
13. network delay simulation (score: 1): Author: Stephen Hemminger <shemminger@xxxxxxxx>; Date: Tue, 16 Mar 2004 15:10:58 -0800; Still bumming around for how to easily simulate long latencies. There is NISTnet but that is fugly old 2.2 code; and Dummynet, and hitbox which are FreeBSD based. The existing traffic shaper might do; /archives/netdev/2004-03/msg00981.html (8,415 bytes)
14. Re: network delay simulation (score: 1): Author: Andi Kleen <ak@xxxxxxx>; Date: Wed, 17 Mar 2004 00:00:48 +0100; iirc there was a 2.4 port of NistNet. Porting it to 2.6 is probably not that much work. -Andi; /archives/netdev/2004-03/msg00982.html (8,912 bytes)
15. Re: network delay simulation (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxx>; Date: Tue, 16 Mar 2004 17:41:34 -0800; Probably a packet scheduler would be my first choice, you could then even tag packets using classification and therefore delay differently for different flows. Another thing I've always wanted to do; /archives/netdev/2004-03/msg00983.html (9,673 bytes)
16. Re: network delay simulation (score: 1): Author: "David S. Miller" <davem@xxxxxxxxxx>; Date: Tue, 16 Mar 2004 17:50:52 -0800; nistnet works, but even akpm remembers it as pretty grotty, who knows maybe the most recent 2.4.x variant was much better, but I doubt it.; /archives/netdev/2004-03/msg00984.html (8,777 bytes)
17. Re: network delay simulation (score: 1): Author: Andi Kleen <ak@xxxxxxx>; Date: Wed, 17 Mar 2004 03:06:34 +0100; For testing it's probably good enough. No need to merge it ;-) -Andi; /archives/netdev/2004-03/msg00985.html (9,291 bytes)
18. Re: network delay simulation (score: 1): Author: Ben Greear <greearb@xxxxxxxxxxxxxxx>; Date: Tue, 16 Mar 2004 18:40:01 -0800; Stephen Hemminger wrote: Still bumming around for how to easily simulate long latencies. There is NISTnet but that is fugly old 2.2 code; and Dummynet, and hitbox which are FreeBSD based. The existin; /archives/netdev/2004-03/msg00986.html (9,876 bytes)
19. Re: network delay simulation (score: 1): Author: John Heffner <jheffner@xxxxxxx>; Date: Wed, 17 Mar 2004 10:37:59 -0500 (EST); One insight I had a while ago is that packet pacing and artificial delay require a very similar mechanism. I hacked something a while ago that did this in a general way, though it had some problems a; /archives/netdev/2004-03/msg01000.html (9,585 bytes)
20. Re: network delay simulation (score: 1): Author: jamal <hadi@xxxxxxxxxx>; Date: 17 Mar 2004 11:09:26 -0500; I had something trying to replace nistnet a while back - probably have to go 10 harddrives back to find it. This is exactly what i had. You need to be able to choose what flow gets affected and which; /archives/netdev/2004-03/msg01001.html (11,168 bytes)

Current List: 1 - 20
Page: [1] [2]