BPF List
 help / color / mirror / Atom feed
From: Kuniyuki Iwashima <kuniyu@amazon.com>
To: <kerneljasonxing@gmail.com>
Cc: <andrii@kernel.org>, <ast@kernel.org>, <bpf@vger.kernel.org>,
	<daniel@iogearbox.net>, <davem@davemloft.net>,
	<dsahern@kernel.org>, <eddyz87@gmail.com>, <edumazet@google.com>,
	<haoluo@google.com>, <horms@kernel.org>,
	<john.fastabend@gmail.com>, <jolsa@kernel.org>,
	<kpsingh@kernel.org>, <kuba@kernel.org>, <kuniyu@amazon.com>,
	<martin.lau@linux.dev>, <ncardwell@google.com>,
	<netdev@vger.kernel.org>, <pabeni@redhat.com>, <sdf@fomichev.me>,
	<song@kernel.org>, <yonghong.song@linux.dev>
Subject: Re: [PATCH net-next 1/3] tcp: add TCP_RTO_MAX_MIN_SEC definition
Date: Thu, 13 Feb 2025 11:19:38 +0900	[thread overview]
Message-ID: <20250213021938.75357-1-kuniyu@amazon.com> (raw)
In-Reply-To: <20250213004355.38918-2-kerneljasonxing@gmail.com>

From: Jason Xing <kerneljasonxing@gmail.com>
Date: Thu, 13 Feb 2025 08:43:52 +0800
> Add minimum value definition as the lower bound of RTO MAX
> set by users. In the next patch, bpf_sol_tcp_setsockopt()
> will use this in the test statement.
> 
> Signed-off-by: Jason Xing <kerneljasonxing@gmail.com>

Reviewed-by: Kuniyuki Iwashima <kuniyu@amazon.com>

  reply	other threads:[~2025-02-13  2:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-13  0:43 [PATCH net-next 0/3] bpf: support setting max RTO for bpf_setsockopt Jason Xing
2025-02-13  0:43 ` [PATCH net-next 1/3] tcp: add TCP_RTO_MAX_MIN_SEC definition Jason Xing
2025-02-13  2:19   ` Kuniyuki Iwashima [this message]
2025-02-13  0:43 ` [PATCH net-next 2/3] bpf: add TCP_BPF_RTO_MAX for bpf_setsockopt Jason Xing
2025-02-13  2:25   ` Kuniyuki Iwashima
2025-02-13  2:32     ` Kuniyuki Iwashima
2025-02-13  3:14       ` Jason Xing
2025-02-13 23:41   ` Stanislav Fomichev
2025-02-13 23:57     ` Jason Xing
2025-02-14  2:14       ` Martin KaFai Lau
2025-02-14  3:09         ` Jason Xing
2025-02-14  5:41           ` Martin KaFai Lau
2025-02-14  6:12             ` Jason Xing
2025-02-14  6:40               ` Martin KaFai Lau
2025-02-14  6:56                 ` Jason Xing
2025-02-14 23:44                   ` Martin KaFai Lau
2025-02-14 23:53                     ` Jason Xing
2025-02-15  2:39                       ` Martin KaFai Lau
2025-02-15  2:52                         ` Jason Xing
2025-02-14 15:48       ` Stanislav Fomichev
2025-02-14 23:21         ` Jason Xing
2025-02-13  0:43 ` [PATCH net-next 3/3] selftests/bpf: add rto max for bpf_setsockopt test Jason Xing
2025-02-13  2:30   ` Kuniyuki Iwashima
2025-02-13  3:13     ` Jason Xing

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=20250213021938.75357-1-kuniyu@amazon.com \
    --to=kuniyu@amazon.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=eddyz87@gmail.com \
    --cc=edumazet@google.com \
    --cc=haoluo@google.com \
    --cc=horms@kernel.org \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kerneljasonxing@gmail.com \
    --cc=kpsingh@kernel.org \
    --cc=kuba@kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sdf@fomichev.me \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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