| To: | Alan Cox <alan@xxxxxxxxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: Q: sock output serialization |
| From: | David Woodhouse <dwmw2@xxxxxxxxxxxxx> |
| Date: | Mon, 18 Sep 2000 12:46:58 +0100 |
| Cc: | hadi@xxxxxxxxxx (jamal), eis@xxxxxxxxxxxxx (Henner Eisen), davem@xxxxxxxxxx, kuznet@xxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <E13aQd5-0002Ej-00@the-village.bc.nu> |
| References: | <E13aQd5-0002Ej-00@the-village.bc.nu> |
| Sender: | owner-netdev@xxxxxxxxxxx |
alan@xxxxxxxxxxxxxxxxxxx said: > I think its fixable to make it do the RR/RNR after bouncing it up the > stack. - ARCnet does ACK in hardware. Packets don't hit the wire until the destination has indicated that it's got a buffer available. You really want to be able to reserve space on the queue before telling the chip to accept another incoming packet - not just realise afterwards that you've screwed up. Strictly speaking, this fact is irrelevant to the case in question, but if we're modifying the generic code for LAPB, we might as well think about other protocols which require similar treatment. -- dwmw2 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | PATCH 2.4.0.9.2: export ethtool interface, Jeff Garzik |
|---|---|
| Next by Date: | ping source code, ychoi |
| Previous by Thread: | Re: Q: sock output serialization, Alan Cox |
| Next by Thread: | Re: Q: sock output serialization, Henner Eisen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |