[lkml]   [2000]   [Sep]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Q: sock output serialization
Date: Fri, 15 Sep 2000 21:07:38 +0400 (MSK DST)

[ Dave, all this sounds bad. ]

Well, there are two things:

1) If exact sequencing is so important, then we can make
special netif_rx tasklet for these guys which serializes
around a spinlock.

Actually, even with this, how could we guarentee this still.
Yes, IRQ affinity would need to force only a single CPU to
receive interrupts from this LAPB device.

It smells rotten to the core, can someone tell me exactly
why reordering is strictly disallowed? I do not even know
how other OSes can handle this properly since most, if
not all, use the IRQ dynamic cpu targeting facilities of
various machines so LAPB is by definition broken there too.

2) Someone please show Alexey and myself how to process input packet
when out of memory and not to drop any packets ;-)

I sense that usually, LAPB handles this issue at a different
level, in the hardware? Does LAPB specify how to maintain
reliably delivery and could we hook into this "how" when we
need to drop LAPB frames? Perhaps it is too late by the time
netif_rx is dealing with it.

LAPB sounds like quite a broken protocol at the moment... But I'm
sure there are details which will emerge and clear this all up.

David S. Miller
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:38    [W:0.061 / U:9.744 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site