| To: | Tommy Christensen <tommy.christensen@xxxxxxxxx> |
|---|---|
| Subject: | Re: [patch 4/10] s390: network driver. |
| From: | Jeff Garzik <jgarzik@xxxxxxxxx> |
| Date: | Sun, 19 Dec 2004 19:15:35 -0500 |
| Cc: | hadi@xxxxxxxxxx, Thomas Spatzier <thomas.spatzier@xxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxxxxx>, Hasso Tepper <hasso@xxxxxxxxx>, Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx, Paul Jakma <paul@xxxxxxxx> |
| In-reply-to: | <41C612BC.5070909@xxxxxxxxx> |
| References: | <OF28701C56.81E1D26E-ONC1256F6B.00513EDD-C1256F6B.0052AF84@xxxxxxxxxx> <1103484552.1046.155.camel@xxxxxxxxxxxxxxxx> <41C600D7.70005@xxxxxxxxx> <1103497516.1046.231.camel@xxxxxxxxxxxxxxxx> <41C612BC.5070909@xxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3) Gecko/20040922 |
Tommy Christensen wrote: It was at least to the same effect. The key issue is whether the packets are kept in the queue (qdisc) until the link is back up, or they are drained (and dropped) by the driver.
They should absolutely not be dropped by the driver. No ifs, ands, or buts.
This sort of problem is NOT solved by modifying hundreds of drivers.
Jeff
|
| Previous by Date: | Re: [patch 4/10] s390: network driver., Paul Jakma |
|---|---|
| Next by Date: | Cheap Prices NOT Cheap Hosting, advertiser |
| Previous by Thread: | Re: [patch 4/10] s390: network driver., Tommy Christensen |
| Next by Thread: | Re: [patch 4/10] s390: network driver., jamal |
| Indexes: | [Date] [Thread] [Top] [All Lists] |