From: Richard Laing <Richard.Laing@alliedtelesis.co.nz>
To: Oleg A Arkhangelsky <sysoleg@yandex.ru>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"pch@ordbogen.com" <pch@ordbogen.com>
Cc: "jmorris@namei.org" <jmorris@namei.org>
Subject: Re: [PATCH 1/1] net/ipv4: Enable flow-based ECMP
Date: Tue, 4 Aug 2015 22:10:05 +0000 [thread overview]
Message-ID: <55C1383C.7070403@alliedtelesis.co.nz> (raw)
In-Reply-To: <1722301438673827@web16h.yandex.ru>
Hi Oleg,
I hadn't seen that patch, thanks, it looks like a pretty thorough solution.
Best Regards,
Richard
On 08/04/2015 07:37 PM, Oleg A Arkhangelsky wrote:
>
> 04.08.2015, 04:29, "Richard Laing" <richard.laing@alliedtelesis.co.nz>:
>> Enable flow-based ECMP.
> Looks like your approach is only restricted to the case when sockets are
> involved. What about forwarded traffic (IP routing case)?
>
> Have you seen similar work done by Peter Nørlund?
>
> http://comments.gmane.org/gmane.linux.kernel.api/12201
>
> --
> wbr, Oleg.
>
> "Anarchy is about taking complete responsibility for yourself."
> Alan Moore.
--
*Richard Laing*
Software Team Leader*
Allied Telesis Labs*| 27 Nazareth Ave | Christchurch 8024 | New Zealand
Phone: +64 3 3393000 | DDI: +64 3 339 9248 | Web: *alliedtelesis.com
<http://alliedtelesis.com/>*<skype:andrewriddell3?chat>
http://productselector.alliedtelesis.eu/
<http://productselector.alliedtelesis.eu/>
next prev parent reply other threads:[~2015-08-04 22:10 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 1:28 [PATCH 1/1] net/ipv4: Enable flow-based ECMP Richard Laing
2015-08-04 5:31 ` Stephen Hemminger
2015-08-04 22:07 ` Richard Laing
2015-08-04 7:37 ` Oleg A Arkhangelsky
2015-08-04 22:10 ` Richard Laing [this message]
2015-08-04 22:25 ` Tom Herbert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55C1383C.7070403@alliedtelesis.co.nz \
--to=richard.laing@alliedtelesis.co.nz \
--cc=jmorris@namei.org \
--cc=netdev@vger.kernel.org \
--cc=pch@ordbogen.com \
--cc=sysoleg@yandex.ru \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).