All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Lytkin <iprintercanon@gmail.com>
To: Eric Dumazet <edumazet@google.com>
Cc: Ido Schimmel <idosch@nvidia.com>,
	David Ahern <dsahern@kernel.org>,
	Lorenzo Bianconi <lorenzo.bianconi@oss.qualcomm.com>,
	Zixuan Chai <petalzu987@gmail.com>, Ren Wei <weir@nebusec.ai>,
	Kuniyuki Iwashima <kuniyu@google.com>,
	netdev@vger.kernel.org
Subject: Re: [PATCH net v4 1/1] ip6_tunnel: snapshot encap in xmit
Date: Mon,  7 Sep 2026 01:43:00 +0300	[thread overview]
Message-ID: <20260906224300.21884-1-iprintercanon@gmail.com> (raw)
In-Reply-To: <CANn89iKeNgRxhkUvxeMmyAJGcT+3hpbWaM+VubQ2sBVGSDeouw@mail.gmail.com>

On Sun, Sep 06, 2026 at 07:54:34PM +0200, Eric Dumazet wrote:
> The general answer is : convert tunnels to RCU based configuration.
> In my quest for RTNL-less ip link dumps, I converted SIT tunnels to
> RCU configuration.

I have ip6_tunnel and ip6_gre done the same way, after your geneve
conversion: the encap and header lengths in a config under an __rcu
pointer, changelink validates and then publishes, fill_info without
RTNL. Seven patches, built and sparse clean, waiting for the nebusec
fix to reach net-next so I can rebase on it. I mentioned it on the v2
thread two weeks ago:

  https://lore.kernel.org/netdev/20260824194741.215979-1-iprintercanon@gmail.com/

Two things I'd like to line up with your sit series. Your patch 2 and
my first one both touch ip_tunnel_encap_setup() and the encap ops in
ip_tunnels.h, so I'd rather rebase on yours; is it close to posting?
And you put sit_parms under RCU as well, while I kept parms out of the
first round because it keys the hash. If you'd rather have parms in
from the start, I'll do that instead of a second series.

Artem

  parent reply	other threads:[~2026-09-06 22:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-05 10:01 [PATCH net v4 0/1] ip6_tunnel: snapshot encap in xmit Ren Wei
2026-09-05 10:01 ` [PATCH net v4 1/1] " Ren Wei
2026-09-06 15:14   ` Ido Schimmel
2026-09-06 17:36   ` Lorenzo Bianconi
2026-09-06 17:54     ` Eric Dumazet
2026-09-06 18:01       ` Lorenzo Bianconi
2026-09-06 22:43       ` Artem Lytkin [this message]
2026-09-07  6:32         ` Eric Dumazet
2026-09-08  8:50           ` Zixuan Chai
2026-09-08  8:57             ` Eric Dumazet

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=20260906224300.21884-1-iprintercanon@gmail.com \
    --to=iprintercanon@gmail.com \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=idosch@nvidia.com \
    --cc=kuniyu@google.com \
    --cc=lorenzo.bianconi@oss.qualcomm.com \
    --cc=netdev@vger.kernel.org \
    --cc=petalzu987@gmail.com \
    --cc=weir@nebusec.ai \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.