| To: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
|---|---|
| Subject: | Re: [RFC/PATCH] "strict" ipv4 reassembly |
| From: | Andi Kleen <ak@xxxxxx> |
| Date: | 17 May 2005 22:27:30 +0200 |
| Date: | Tue, 17 May 2005 22:27:30 +0200 |
| Cc: | dlstevens@xxxxxxxxxx, akepner@xxxxxxx, jheffner@xxxxxxx, netdev@xxxxxxxxxxx, netdev-bounce@xxxxxxxxxxx |
| In-reply-to: | <20050517.132202.59028935.davem@xxxxxxxxxxxxx> |
| References: | <m1sm0l7jcl.fsf@xxxxxx> <OF0221F508.AD091D99-ON88257004.006D0C52-88257004.006D8293@xxxxxxxxxx> <m1k6lx7gkf.fsf@xxxxxx> <20050517.132202.59028935.davem@xxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.4.1i |
On Tue, May 17, 2005 at 01:22:02PM -0700, David S. Miller wrote: > 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. :-) Arghl, you said the "i" word.... Anyways, I think the neighbour cache is fully appropiate, is it not? But it's not clear such a hack would be worth it anyways. If anything it would be probably better to let mountd set the RTTs, e.g. implicitely with MSG_CONFIRM (I hope it is using it these days ...) -Andi |
| Previous by Date: | Re: [RFC/PATCH] "strict" ipv4 reassembly, Arthur Kepner |
|---|---|
| Next by Date: | Re: [RFC/PATCH] "strict" ipv4 reassembly, John Heffner |
| Previous by Thread: | Re: [RFC/PATCH] "strict" ipv4 reassembly, David S. Miller |
| Next by Thread: | Re: [RFC/PATCH] "strict" ipv4 reassembly, David S. Miller |
| Indexes: | [Date] [Thread] [Top] [All Lists] |