[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL+tcoDD-byX4hNWUpDTv6aPPzt3AMHbgZp30V2abADphf7JbQ@mail.gmail.com>
Date: Tue, 25 Mar 2025 00:57:29 +0800
From: Jason Xing <kerneljasonxing@...il.com>
To: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, horms@...nel.org, ncardwell@...gle.com, kuniyu@...zon.com,
dsahern@...nel.org
Cc: netdev@...r.kernel.org
Subject: Re: [PATCH net-next v4 0/2] support TCP_RTO_MIN_US and
TCP_DELACK_MAX_US for set/getsockopt
On Tue, Mar 25, 2025 at 12:35 AM Jason Xing <kerneljasonxing@...il.com> wrote:
>
> On Mon, Mar 17, 2025 at 8:03 PM Jason Xing <kerneljasonxing@...il.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
> >
Powered by blists - more mailing lists