| To: | hadi@xxxxxxxxxx (jamal) |
|---|---|
| Subject: | Re: Q: sock output serialization |
| From: | Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> |
| Date: | Sat, 16 Sep 2000 23:40:13 +0100 (BST) |
| Cc: | eis@xxxxxxxxxxxxx (Henner Eisen), alan@xxxxxxxxxxxxxxxxxxx, davem@xxxxxxxxxx, kuznet@xxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <Pine.GSO.4.20.0009161805100.9880-100000@shell.cyberus.ca> from "jamal" at Sep 16, 2000 06:38:49 PM |
| Sender: | owner-netdev@xxxxxxxxxxx |
> > With the current scheme, lapb first acknowleges reception of the frame > > and after that, netif_rx() might still discard it -- which is evil. > > This might screw things a bit. Can you defer to say first call > netif_rx() then acknowledge or is this hard-coded into the f/ware? I think its fixable to make it do the RR/RNR after bouncing it up the stack. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Q: sock output serialization, jamal |
|---|---|
| Next by Date: | Re: Q: sock output serialization, Andi Kleen |
| Previous by Thread: | Re: Q: sock output serialization, jamal |
| Next by Thread: | Re: Q: sock output serialization, David Woodhouse |
| Indexes: | [Date] [Thread] [Top] [All Lists] |