BPF List
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>,
	Matthieu Baerts <matttbe@kernel.org>
Cc: Martin KaFai Lau <martin.lau@linux.dev>,
	Network Development <netdev@vger.kernel.org>,
	bpf <bpf@vger.kernel.org>, MPTCP Upstream <mptcp@lists.linux.dev>,
	Mat Martineau <martineau@kernel.org>,
	Jakub Kicinski <kuba@kernel.org>,
	Martin KaFai Lau <martin.lau@kernel.org>,
	Geliang Tang <geliang@kernel.org>
Subject: Re: mptcp splat
Date: Fri, 29 Mar 2024 17:34:07 +0100	[thread overview]
Message-ID: <2ee8745cfa411fa2c397af8b1323f77e1bd00d29.camel@redhat.com> (raw)
In-Reply-To: <CAADnVQJxsqbJgu9K-ML2-1tRcgEmHY-UuQOCDxqv8_6iVkW7Tg@mail.gmail.com>

On Fri, 2024-03-29 at 09:26 -0700, Alexei Starovoitov wrote:
> On Thu, Mar 28, 2024 at 10:35 AM Matthieu Baerts <matttbe@kernel.org> wrote:
> > 
> > Hi Martin,
> > 
> > On 27/03/2024 23:16, Martin KaFai Lau wrote:
> > 
> > (...)
> > 
> > > Unrelated, is there a way to tell if a tcp_sock is a subflow?
> > 
> > Yes, you can use "sk_is_mptcp(sk)". Please note that this 'sk' *has* to
> > be a tcp_sock, this is not checked by the helper.
> > 
> > That's what is used with bpf_mptcp_sock_from_subflow()
> > 
> > https://elixir.bootlin.com/linux/latest/source/net/mptcp/bpf.c#L15
> > 
> > > bpf prog
> > > can use it to decide if it wants to setsockopt on a subflow or not.
> > I think it is important to keep the possibility to set socket options
> > per subflow. If the original issue discussed here is limited to
> > set_rcvlowat(), best to address it there.
> 
> 
> All makes sense to me.
> 
> Paolo,
> could you send an official patch?

Sure, thank you for reminding me. This was falling off my radar. I'll
send it after some testing.

Thanks!

Paolo


      reply	other threads:[~2024-03-29 16:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-27 16:43 mptcp splat Alexei Starovoitov
2024-03-27 16:56 ` Paolo Abeni
2024-03-27 17:00   ` Alexei Starovoitov
2024-03-27 18:32     ` Paolo Abeni
2024-03-27 18:45       ` Mat Martineau
2024-03-27 18:50       ` Alexei Starovoitov
2024-03-27 22:16         ` Martin KaFai Lau
2024-03-28 17:35           ` Matthieu Baerts
2024-03-29 16:26             ` Alexei Starovoitov
2024-03-29 16:34               ` Paolo Abeni [this message]

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=2ee8745cfa411fa2c397af8b1323f77e1bd00d29.camel@redhat.com \
    --to=pabeni@redhat.com \
    --cc=alexei.starovoitov@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=geliang@kernel.org \
    --cc=kuba@kernel.org \
    --cc=martin.lau@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=martineau@kernel.org \
    --cc=matttbe@kernel.org \
    --cc=mptcp@lists.linux.dev \
    --cc=netdev@vger.kernel.org \
    /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