| To: | ak@xxxxxx |
|---|---|
| Subject: | Re: [RFC/PATCH] "strict" ipv4 reassembly |
| From: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
| Date: | Tue, 17 May 2005 13:22:02 -0700 (PDT) |
| Cc: | dlstevens@xxxxxxxxxx, akepner@xxxxxxx, jheffner@xxxxxxx, netdev@xxxxxxxxxxx, netdev-bounce@xxxxxxxxxxx |
| In-reply-to: | <m1k6lx7gkf.fsf@xxxxxx> |
| References: | <m1sm0l7jcl.fsf@xxxxxx> <OF0221F508.AD091D99-ON88257004.006D0C52-88257004.006D8293@xxxxxxxxxx> <m1k6lx7gkf.fsf@xxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
From: Andi Kleen <ak@xxxxxx> Date: Tue, 17 May 2005 22:17:36 +0200 > At least for a directly connected flat network you could get it from ARP. So we can make this host based, and store that "arp RTT" thing in the inetpeer cache. :-) |
| Previous by Date: | Re: [RFC/PATCH] "strict" ipv4 reassembly, Andi Kleen |
|---|---|
| Next by Date: | Re: [RFC/PATCH] "strict" ipv4 reassembly, Arthur Kepner |
| 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] |