On Tue, 2004-03-16 at 20:41, David S. Miller wrote:
> > Any ideas/comments? Somebody have some code sitting in a drawer?
I had something trying to replace nistnet a while back - probably
have to go 10 harddrives back to find it.
> Probably a packet scheduler would be my first choice, you could then even
> tag packets using classification and therefore delay differently for different
This is exactly what i had. You need to be able to choose what flow gets
affected and which ones are left alone.
A better approach is to use the action code patches i have because then
you can cascade actions that you want and keep adding new error
example delay for random time between 30 seconds to 1 minute, then fuck
the checksum, then simulate congestion ... with each of those actions
selectable on how it gets added to the datapath.
> Another thing I've always wanted to do was add a "struct netdev *" argument
> to dev_alloc_skb(), then we could do things like do SKB allocation failure
> tests on drivers to stress them in low memory situations and weird patterns
> of alloc failures. Probably do this in a transitional way via a new routine
> with a new name that drivers gradually move over to using.
this is valuable. I can bet you over 70% of the drivers will puke like
theres no tommorow.
Not just that, the net stack code will too.
> The idea is that we provide an interface by which to upload some bit string
> of alloc success/failure binary states, and at each alloc the state machine
> just runs through the bits to decide whether to just quickly return NULL or
A simple algorithm is random().