From: Valentin Schneider <vschneid@redhat.com>
To: dccp@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
mleitner@redhat.com, David Ahern <dsahern@kernel.org>,
Juri Lelli <juri.lelli@redhat.com>,
Tomas Glozar <tglozar@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH v3 0/1] tcp/dcpp: Un-pin tw_timer
Date: Mon, 19 Feb 2024 10:57:28 +0100 [thread overview]
Message-ID: <20240219095729.2339914-1-vschneid@redhat.com> (raw)
Hi,
This is v3 of the series where the tw_timer is un-pinned to get rid of interferences in
isolated CPUs setups.
Eric mentionned rsk_timer needs looking into, but I haven't had the time to do
that. It doesn't show up in our testing, which might be due to its relatively
low timeout (IIUC 3s).
Revisions
=========
RFCv1 -> v2
++++++++
o Added comment in inet_twsk_deschedule_put() to highlight the race
o Added bh_disable patch
v2 -> v3
++++++++
o Dropped bh_disable patch
o Rebased against latest Linus' tree
Valentin Schneider (1):
tcp/dcpp: Un-pin tw_timer
net/dccp/minisocks.c | 16 +++++++---------
net/ipv4/inet_timewait_sock.c | 20 +++++++++++++++-----
net/ipv4/tcp_minisocks.c | 16 +++++++---------
3 files changed, 29 insertions(+), 23 deletions(-)
--
2.43.0
next reply other threads:[~2024-02-19 9:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 9:57 Valentin Schneider [this message]
2024-02-19 9:57 ` [PATCH v3 1/1] tcp/dcpp: Un-pin tw_timer Valentin Schneider
2024-02-19 14:42 ` Eric Dumazet
2024-02-20 17:38 ` Valentin Schneider
2024-02-20 17:42 ` Eric Dumazet
2024-02-21 16:45 ` Valentin Schneider
2024-03-21 19:03 ` Paolo Abeni
2024-03-22 20:58 ` Valentin Schneider
2024-03-25 15:15 ` Paolo Abeni
2024-02-19 18:55 ` Kuniyuki Iwashima
2024-02-20 17:38 ` Valentin Schneider
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=20240219095729.2339914-1-vschneid@redhat.com \
--to=vschneid@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=dccp@vger.kernel.org \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=juri.lelli@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mleitner@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tglozar@redhat.com \
--cc=tglx@linutronix.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).