Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1507043
| From | Hannes Frederic Sowa <hannes@stressinduktion.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH net-next 3/5] ipv6: Use multipath hash from flow info if available |
| Date | 2016-10-24 11:50 +0200 |
| Message-ID | <svK3f-5Kp-17@gated-at.bofh.it> (permalink) |
| References | <svJJT-5DE-5@gated-at.bofh.it> <svJJU-5DE-23@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 24.10.2016 11:28, Jakub Sitnicki wrote: > Allow our callers to influence the choice of ECMP link by honoring the > hash passed together with the flow info. This will allow for special > treatment of ICMP errors which we would like to route over the same link > as the IP datagram that triggered the error. > > Signed-off-by: Jakub Sitnicki <jkbs@redhat.com> Acked-by: Hannes Frederic Sowa <hannes@stressinduktion.org>
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH net-next 0/5] Route ICMPv6 errors with the flow when ECMP in use Jakub Sitnicki <jkbs@redhat.com> - 2016-10-24 11:30 +0200
[PATCH net-next 3/5] ipv6: Use multipath hash from flow info if available Jakub Sitnicki <jkbs@redhat.com> - 2016-10-24 11:30 +0200
Re: [PATCH net-next 3/5] ipv6: Use multipath hash from flow info if available Hannes Frederic Sowa <hannes@stressinduktion.org> - 2016-10-24 11:50 +0200
[PATCH net-next 2/5] net: Extend struct flowi6 with multipath hash Jakub Sitnicki <jkbs@redhat.com> - 2016-10-24 11:30 +0200
Re: [PATCH net-next 2/5] net: Extend struct flowi6 with multipath hash Hannes Frederic Sowa <hannes@stressinduktion.org> - 2016-10-24 11:40 +0200
[PATCH net-next 1/5] ipv6: Fold rt6_info_hash_nhsfn() into its only caller Jakub Sitnicki <jkbs@redhat.com> - 2016-10-24 11:40 +0200
csiph-web