| To: | David Stevens <dlstevens@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [RFC/PATCH] "strict" ipv4 reassembly |
| From: | Andi Kleen <ak@xxxxxx> |
| Date: | Tue, 17 May 2005 22:17:36 +0200 |
| Cc: | akepner@xxxxxxx, "David S. Miller" <davem@xxxxxxxxxxxxx>, John Heffner <jheffner@xxxxxxx>, netdev@xxxxxxxxxxx, netdev-bounce@xxxxxxxxxxx |
| In-reply-to: | <OF0221F508.AD091D99-ON88257004.006D0C52-88257004.006D8293@xxxxxxxxxx> (David Stevens's message of "Tue, 17 May 2005 12:56:05 -0700") |
| References: | <m1sm0l7jcl.fsf@xxxxxx> <OF0221F508.AD091D99-ON88257004.006D0C52-88257004.006D8293@xxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (gnu/linux) |
David Stevens <dlstevens@xxxxxxxxxx> writes: > 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. :-) At least for a directly connected flat network you could get it from ARP. -Andi |
| Previous by Date: | Re: [RFC/PATCH] "strict" ipv4 reassembly, Rick Jones |
|---|---|
| Next by Date: | Re: [RFC/PATCH] "strict" ipv4 reassembly, David S. Miller |
| Previous by Thread: | Re: [RFC/PATCH] "strict" ipv4 reassembly, David Stevens |
| Next by Thread: | Re: [RFC/PATCH] "strict" ipv4 reassembly, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |