On Wed, 2005-01-05 at 01:30, Paul Jakma wrote:
> On Wed, 4 Jan 2005, jamal wrote:
> > Theres possibly people who would want it differently - so for we
> > havent heard from them. Maybe poll far and wide - or push it in and
> > wait for them to whine.
> We're whining.
> This policy in the Linux kernel makes using Linux dangerous for
> certain routing applications (RIP, routing advertisements).
> Name a non-TCP application that *does* want this newish kernel policy
> and tell me how it breaks without this *new* policy. ;)
Ok, Iam confused - I thought you guys _wanted this_ ;->
The issue is about message obsolency more than it is about reliability.
Without this the scenario you played you played for us before was:
1)=>send a few LSAs from user space, pull cable before they go out
(this will happen if you are sending sufficiently large amounts of
packets i.e network is busy),
2)=>user space gets notified via netlink, device shuts down acces to
DMA, packets queued anyways and you have no ability to say "ooops,sorry
take that packet back"
a)You could do a move to another device at this point.
b) dumb app will continue sending
3)=>plug cable back in 2 minutes later, obsolete LSAs sent followed by
any new ones that may follow
With the patch, packets in #2 will be dropped. As a matter of fact
within those two minutes, if stopped, it is probable the device watchdog
timer will kick in and flush the DMA but not the scheduler queues above
it (which is where upto a 1000 stale packets could be sitting).
What is it that you dont like now?