|To:||Tommy Christensen <tommy.christensen@xxxxxxxxx>|
|Subject:||Re: [patch 4/10] s390: network driver.|
|From:||Paul Jakma <paul@xxxxxxxx>|
|Date:||Mon, 20 Dec 2004 14:16:47 +0000 (UTC)|
|Cc:||hadi@xxxxxxxxxx, Thomas Spatzier <thomas.spatzier@xxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxxxxx>, Hasso Tepper <hasso@xxxxxxxxx>, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>, jgarzik@xxxxxxxxx, netdev@xxxxxxxxxxx|
|References:||<OF28701C56.81E1D26E-ONC1256F6B.00513EDD-C1256F6B.0052AF84@xxxxxxxxxx> <1103484552.1046.155.camel@xxxxxxxxxxxxxxxx> <41C600D7.70005@xxxxxxxxx> <1103497516.1046.231.camel@xxxxxxxxxxxxxxxx> <41C612BC.5070909@xxxxxxxxx>|
On Mon, 20 Dec 2004, Tommy Christensen wrote:
For a routing protocol that actually is notified that the link went down, it should probably flush those socket buffer at that point.
Or why not return an error, as soon as possible on the socket, eg ENOBUFS, and discard anything in the queue before that. Make it configurable via a sockopt if you think it'd harm ordinary apps (though, anything that cant deal with ENOBUFS is broken already, really..) or make it apply only to nonblock sockets.
responsibility of the application to flush the socket on link-down events (by down'ing the interface?).
That seems more complex than needs be, for userspace at least. regards, -- Paul Jakma paul@xxxxxxxx paul@xxxxxxxxx Key ID: 64A2FF6A Fortune: "Paul Lynde to block..." -- a contestant on "Hollywood Squares"
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||Re: [PATCH] PKT_SCHED: Fix cls indev validation, jamal|
|Next by Date:||Re: [PATCH] PKT_SCHED: Provide compat policer stats in action policer, jamal|
|Previous by Thread:||Re: [patch 4/10] s390: network driver., jamal|
|Next by Thread:||Re: [patch 4/10] s390: network driver., Jeff Garzik|
|Indexes:||[Date] [Thread] [Top] [All Lists]|