| To: | Nivedita Singhvi <niv@xxxxxxxxxx> |
|---|---|
| Subject: | Re: [RFC/PATCH] "strict" ipv4 reassembly |
| From: | John Heffner <jheffner@xxxxxxx> |
| Date: | Tue, 17 May 2005 16:05:20 -0400 |
| Cc: | netdev@xxxxxxxxxxx |
| In-reply-to: | <428A4B74.4050503@us.ibm.com> |
| Organization: | PSC |
| References: | <Pine.LNX.4.61.0505170914130.29021@linux.site> <200505171531.37167.jheffner@psc.edu> <428A4B74.4050503@us.ibm.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | KMail/1.8 |
On Tuesday 17 May 2005 03:52 pm, Nivedita Singhvi wrote: > John Heffner wrote: > > On Tuesday 17 May 2005 03:25 pm, Nivedita Singhvi wrote: > >>Yes, a different manifestation of the problem ;). I was talking > >>in the context of current Linux code and the common ethernet drivers > >>and typical current Internet/Intranet latencies. > > > > The problem is latency independent. > > Not entirely - because our reassembly timeout expires, typically. > (If I understand you right). Timer expiration is not dependent on latency, nor is IP ID wrap time. -John |
| Previous by Date: | Re: [RFC/PATCH] "strict" ipv4 reassembly, David Stevens |
|---|---|
| Next by Date: | Re: [RFC/PATCH] "strict" ipv4 reassembly, Rick Jones |
| Previous by Thread: | Re: [RFC/PATCH] "strict" ipv4 reassembly, Nivedita Singhvi |
| Next by Thread: | Re: [RFC/PATCH] "strict" ipv4 reassembly, Rick Jones |
| Indexes: | [Date] [Thread] [Top] [All Lists] |