[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210722145341.72566-1-kuniyu@amazon.co.jp>
Date: Thu, 22 Jul 2021 23:53:41 +0900
From: Kuniyuki Iwashima <kuniyu@...zon.co.jp>
To: <kafai@...com>
CC: <ast@...nel.org>, <bpf@...r.kernel.org>, <daniel@...earbox.net>,
<edumazet@...gle.com>, <kernel-team@...com>,
<ncardwell@...gle.com>, <netdev@...r.kernel.org>,
<ycheng@...gle.com>, <yhs@...com>, <kuniyu@...zon.co.jp>
Subject: Re: [PATCH v2 bpf-next 0/8] bpf: Allow bpf tcp iter to do bpf_(get|set)sockopt
From: Martin KaFai Lau <kafai@...com>
Date: Thu, 1 Jul 2021 13:05:35 -0700
> This set is to allow bpf tcp iter to call bpf_(get|set)sockopt.
>
> With bpf-tcp-cc, new algo rollout happens more often. Instead of
> restarting the applications to pick up the new tcp-cc, this set
> allows the bpf tcp iter to call bpf_(get|set)sockopt(TCP_CONGESTION).
> It is not limited to TCP_CONGESTION, the bpf tcp iter can call
> bpf_(get|set)sockopt() with other options. The bpf tcp iter can read
> into all the fields of a tcp_sock, so there is a lot of flexibility
> to select the desired sk to do setsockopt(), e.g. it can test for
> TCP_LISTEN only and leave the established connections untouched,
> or check the addr/port, or check the current tcp-cc name, ...etc.
>
> Patch 1-4 are some cleanup and prep work in the tcp and bpf seq_file.
>
> Patch 5 is to have the tcp seq_file iterate on the
> port+addr lhash2 instead of the port only listening_hash.
>
> Patch 6 is to have the bpf tcp iter doing batching which
> then allows lock_sock. lock_sock is needed for setsockopt.
>
> Patch 7 allows the bpf tcp iter to call bpf_(get|set)sockopt.
I have a comment on the first patch, but the series looks good to me.
Acked-by: Kuniyuki Iwashima <kuniyu@...zon.co.jp>
Powered by blists - more mailing lists