| To: | hadi@xxxxxxxxxx |
|---|---|
| Subject: | Re: [RFC][PATCH 2/2] ip multipath, bk head (EXPERIMENTAL) |
| From: | "David S. Miller" <davem@xxxxxxxxxxxxx> |
| Date: | Mon, 13 Sep 2004 22:42:32 -0700 |
| Cc: | lkml@xxxxxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx |
| In-reply-to: | <1095129624.1060.45.camel@xxxxxxxxxxxxxxxx> |
| References: | <41457848.6040808@xxxxxxxxxx> <1095129624.1060.45.camel@xxxxxxxxxxxxxxxx> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
On 13 Sep 2004 22:40:24 -0400 jamal <hadi@xxxxxxxxxx> wrote: > As long as whatever arrangement ensures that no packet reordering > happens, should be sane. Yes, current scheme is broken in some ways (but > guarantees packet ordering within a flow). I think his changes ensure this as well, at least for local system sockets. You'll only get a new hop each time a route lookup is performed, which is only done once per socket unless the path becomes "sick" and TCP decides to try and do a relookup of the destination. I'm kind of ambivalent about these changes. I definitely like the first patch which cleans up those huge functions in route.c :-) But there are things I like about the current behavior, although I understand why people want things to work the way Einar is changing it to. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: generic 802.11 stack, David S. Miller |
|---|---|
| Next by Date: | Re: [PATCH 2.6] ip_nat_ftp - manip at the right place, Harald Welte |
| Previous by Thread: | Re: [RFC][PATCH 2/2] ip multipath, bk head (EXPERIMENTAL), jamal |
| Next by Thread: | Re: [RFC][PATCH 2/2] ip multipath, bk head (EXPERIMENTAL), jamal |
| Indexes: | [Date] [Thread] [Top] [All Lists] |