From: Jason Xing <kerneljasonxing@gmail.com>
To: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, ncardwell@google.com,
kuniyu@amazon.com, dsahern@kernel.org
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next v4 0/2] support TCP_RTO_MIN_US and TCP_DELACK_MAX_US for set/getsockopt
Date: Tue, 25 Mar 2025 00:57:29 +0800 [thread overview]
Message-ID: <CAL+tcoDD-byX4hNWUpDTv6aPPzt3AMHbgZp30V2abADphf7JbQ@mail.gmail.com> (raw)
In-Reply-To: <CAL+tcoA6uawe99jrkRugrPmgEOsnCAgcqak-2uBO80jMDB+SHg@mail.gmail.com>
On Tue, Mar 25, 2025 at 12:35 AM Jason Xing <kerneljasonxing@gmail.com> wrote:
>
> On Mon, Mar 17, 2025 at 8:03 PM Jason Xing <kerneljasonxing@gmail.com> wrote:
> >
> > Add set/getsockopt supports for TCP_RTO_MIN_US and TCP_DELACK_MAX_US.
> >
> > v4
> > 1. add more detailed information into commit log (Eric)
> > 2. use val directly in do_tcp_getsockopt (Eric)
> >
> > Jason Xing (2):
> > tcp: support TCP_RTO_MIN_US for set/getsockopt use
> > tcp: support TCP_DELACK_MAX_US for set/getsockopt use
>
> Gentle ping here :) I noticed that net-next is closed, so I decided to
> reply to this thread.
Oh, I should have noticed that most of the core maintainers are absent
these days. Sorry, I don't expect to add more burden so I can resend
after net-next is open. Anyway, either way is fine with me. Just
please let me know :)
Thank you.
>
> Thanks,
> Jason
>
> >
> > Documentation/networking/ip-sysctl.rst | 4 ++--
> > include/net/tcp.h | 2 +-
> > include/uapi/linux/tcp.h | 2 ++
> > net/ipv4/tcp.c | 26 ++++++++++++++++++++++++--
> > net/ipv4/tcp_output.c | 2 +-
> > 5 files changed, 30 insertions(+), 6 deletions(-)
> >
> > --
> > 2.43.5
> >
next prev parent reply other threads:[~2025-03-24 16:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-17 12:03 [PATCH net-next v4 0/2] support TCP_RTO_MIN_US and TCP_DELACK_MAX_US for set/getsockopt Jason Xing
2025-03-17 12:03 ` [PATCH net-next v4 1/2] tcp: support TCP_RTO_MIN_US for set/getsockopt use Jason Xing
2025-03-25 11:09 ` Eric Dumazet
2025-03-17 12:03 ` [PATCH net-next v4 2/2] tcp: support TCP_DELACK_MAX_US " Jason Xing
2025-03-25 11:13 ` Eric Dumazet
2025-03-26 11:54 ` Jason Xing
2025-03-24 16:35 ` [PATCH net-next v4 0/2] support TCP_RTO_MIN_US and TCP_DELACK_MAX_US for set/getsockopt Jason Xing
2025-03-24 16:57 ` Jason Xing [this message]
2025-03-25 11:40 ` patchwork-bot+netdevbpf
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=CAL+tcoDD-byX4hNWUpDTv6aPPzt3AMHbgZp30V2abADphf7JbQ@mail.gmail.com \
--to=kerneljasonxing@gmail.com \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=kuniyu@amazon.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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;
as well as URLs for NNTP newsgroup(s).