From: David Ahern <dsahern@kernel.org>
To: azey <me@azey.net>
Cc: nicolasdichtel <nicolas.dichtel@6wind.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Simon Horman <horms@kernel.org>, netdev <netdev@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] net/ipv6: allow device-only routes via the multipath API
Date: Tue, 18 Nov 2025 11:18:34 -0700 [thread overview]
Message-ID: <07f075bd-46a7-4298-953f-d0540759d694@kernel.org> (raw)
In-Reply-To: <19a97dce5fc.10e4ece0319525.6646442146487396729@azey.net>
On 11/18/25 9:47 AM, azey wrote:
> On 2025-11-18 17:04:38 +0100, David Ahern <dsahern@kernel.org> wrote:
>> There is really no reason to take a risk of a regression. If someone
>> wants ecmp with device only nexthops, then use the new nexthop infra to
>> do it.
>
> My initial reason was that device-only ECMP via `ip route` works with IPv4
> but not IPv6, so I thought it'd make sense to unify functionality - but if
> this is final I won't argue any further.
>
There was a push many years ago to align v4 and v6 as much as possible.
Certain areas - like ipv6 multipath - proved to be too difficult and
ended up causing regressions.
next prev parent reply other threads:[~2025-11-18 18:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-16 18:31 [PATCH] net/ipv6: allow device-only routes via the multipath API azey
2025-11-17 1:57 ` David Ahern
2025-11-18 9:05 ` Nicolas Dichtel
2025-11-18 11:00 ` azey
2025-11-18 16:04 ` David Ahern
2025-11-18 16:41 ` Nicolas Dichtel
2025-11-18 16:58 ` azey
2025-11-18 16:47 ` azey
2025-11-18 18:18 ` David Ahern [this message]
2025-11-17 23:51 ` kernel test robot
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=07f075bd-46a7-4298-953f-d0540759d694@kernel.org \
--to=dsahern@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=me@azey.net \
--cc=netdev@vger.kernel.org \
--cc=nicolas.dichtel@6wind.com \
--cc=pabeni@redhat.com \
/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