| To: | Andi Kleen <ak@xxxxxx> |
|---|---|
| Subject: | Re: [RFC/PATCH] "strict" ipv4 reassembly |
| From: | David Stevens <dlstevens@xxxxxxxxxx> |
| Date: | Tue, 17 May 2005 12:56:05 -0700 |
| Cc: | akepner@xxxxxxx, "David S. Miller" <davem@xxxxxxxxxxxxx>, John Heffner <jheffner@xxxxxxx>, netdev@xxxxxxxxxxx, netdev-bounce@xxxxxxxxxxx |
| In-reply-to: | <m1sm0l7jcl.fsf@muc.de> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
Dave,
Shouldn't that be an estimator on the destination RTT? Or is that
what you meant? A fast link locally that traverses a slow path along the
way
would time out too fast.
Of course, getting an RTT estimate if there hasn't been TCP
traffic
is a complication. :-)
+-DLS
|
| Previous by Date: | Re: [RFC/PATCH] "strict" ipv4 reassembly, Andi Kleen |
|---|---|
| Next by Date: | Re: [RFC/PATCH] "strict" ipv4 reassembly, John Heffner |
| Previous by Thread: | Re: [RFC/PATCH] "strict" ipv4 reassembly, Andi Kleen |
| Next by Thread: | Re: [RFC/PATCH] "strict" ipv4 reassembly, Andi Kleen |
| Indexes: | [Date] [Thread] [Top] [All Lists] |