> > 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: Q: sock output serialization kuznet
- Re: Q: sock output serialization David S. Miller
- Re: Q: sock output serialization Alan Cox
- Re: Q: sock output serialization Henner Eisen
- Re: Q: sock output serialization Alan Cox
- Re: Q: sock output serialization Henner Eisen
- Re: Q: sock output serialization kuznet
- Re: Q: sock output serialization Henner Eisen
- Re: Q: sock output serialization Henner Eisen
- Re: Q: sock output serialization jamal
- Re: Q: sock output serialization Alan Cox
- Re: Q: sock output serialization David Woodhouse
- Re: Q: sock output serialization Henner Eisen
- Re: Q: sock output serialization jamal
- Re: Q: sock output serialization Henner Eisen
- Re: Q: sock output serialization jamal
- Re: Q: sock output serialization Henner Eisen
- Re: Q: sock output serialization Andi Kleen
- Re: Q: sock output serialization Henner Eisen