[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210520085435.48836-1-kuniyu@amazon.co.jp>
Date: Thu, 20 May 2021 17:54:35 +0900
From: Kuniyuki Iwashima <kuniyu@...zon.co.jp>
To: <kafai@...com>
CC: <andrii@...nel.org>, <ast@...nel.org>, <benh@...zon.com>,
<bpf@...r.kernel.org>, <daniel@...earbox.net>,
<davem@...emloft.net>, <edumazet@...gle.com>, <kuba@...nel.org>,
<kuni1840@...il.com>, <kuniyu@...zon.co.jp>,
<linux-kernel@...r.kernel.org>, <netdev@...r.kernel.org>
Subject: Re: [PATCH v6 bpf-next 09/11] bpf: Support socket migration by eBPF.
From: Martin KaFai Lau <kafai@...com>
Date: Wed, 19 May 2021 23:27:23 -0700
> On Mon, May 17, 2021 at 09:22:56AM +0900, Kuniyuki Iwashima wrote:
> > This patch introduces a new bpf_attach_type for BPF_PROG_TYPE_SK_REUSEPORT
> > to check if the attached eBPF program is capable of migrating sockets. When
> > the eBPF program is attached, we run it for socket migration if the
> > expected_attach_type is BPF_SK_REUSEPORT_SELECT_OR_MIGRATE or
> > net.ipv4.tcp_migrate_req is enabled.
> >
> > Ccurrently, the expected_attach_type is not enforced for the
> nit. 'Currenctly,'
Thank you, I'll fix it to 'Currently' :)
Powered by blists - more mailing lists