| To: | Jeff Garzik <jgarzik@xxxxxxxxx> |
|---|---|
| Subject: | Re: [patch 4/10] s390: network driver. |
| From: | Paul Jakma <paul@xxxxxxxx> |
| Date: | Mon, 15 Nov 2004 07:52:50 +0000 (GMT) |
| Cc: | Thomas Spatzier <thomas.spatzier@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, Netdev <netdev@xxxxxxxxxxx> |
| In-reply-to: | <4196B4E9.40502@pobox.com> |
| Mail-followup-to: | paul@xxxxxxxxxxxxxxxxxx |
| References: | <OF88EC0E9F.DE8FC278-ONC1256F4A.0038D5C0-C1256F4A.00398E11@de.ibm.com> <4196B4E9.40502@pobox.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On Sat, 13 Nov 2004, Jeff Garzik wrote: Queues are DESIGNED to fill up under various conditions. What happens when they are full? Blocking isnt good, at least not from GNU Zebra / Quagga's POV. Would not the zebra routing software have the same problems with cable pull under an e1000 or tg3 gigabit NIC?
The most popular drivers -- e1000, tg3, etc. -- do not do this, for very good reasons. The problem is that GNU Zebra / Quagga uses a single raw socket for certain protocols, eg OSPF. Blocking the socket because one NIC has a cable pulled is undesireable, and there's no point queueing the packets, by the time the link comes back, if ever, its highly unlikely there is any use in sending the packets (sending OSPF hello's from X minutes ago on a link that just came back is useless). The kernel really shouldnt get too much in the way of an application that already is fully aware of reliability issues[1] - at least that is the application's expectation in this case. We could change it to use a socket/interface on Linux, but it seems a bit unnecessary to me, at least for raw socket/included-header sockets. Jeff 1. an application must be if its uses raw sockets surely? Even for non-raw/header-included sockets, eg BGP tcp sockets, a user like GNU Zebra / Quagga would much prefer packets to be dropped. regards, -- Paul Jakma paul@xxxxxxxx paul@xxxxxxxxx Key ID: 64A2FF6A Fortune: My interest is in the future because I am going to spend the rest of my life there. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [netdrvr] netdev-2.6 queue updated, Wichert Akkerman |
|---|---|
| Next by Date: | RE: [netdrvr] netdev-2.6 queue updated, Zhu, Yi |
| Previous by Thread: | Re: [patch 4/10] s390: network driver., Jeff Garzik |
| Next by Thread: | Re: [patch 4/10] s390: network driver., Paul Jakma |
| Indexes: | [Date] [Thread] [Top] [All Lists] |