From: Allison Henderson <achender@kernel.org>
To: netdev@vger.kernel.org
Cc: linux-kselftest@vger.kernel.org, pabeni@redhat.com,
edumazet@google.com, rds-devel@oss.oracle.com, kuba@kernel.org,
horms@kernel.org, linux-rdma@vger.kernel.org,
allison.henderson@oracle.com
Subject: [PATCH net-next v1 0/7] net/rds: RDS-TCP protocol and extension improvements
Date: Sun, 25 Jan 2026 00:06:44 -0700 [thread overview]
Message-ID: <20260125070651.207042-1-achender@kernel.org> (raw)
From: Allison Henderson <allison.henderson@oracle.com>
Hi all,
This is subset 3 of the larger RDS-TCP patch series I posted last
Oct. The greater series aims to correct multiple rds-tcp issues that
can cause dropped or out of sequence messages. I've broken it down into
smaller sets to make reviews more manageable.
In this set, we introduce extension headers for byte accounting
and fix several RDS/TCP protocol issues including message preservation
during connection transitions and multipath lane handling.
The entire set can be viewed in the rfc here:
https://lore.kernel.org/netdev/20251022191715.157755-1-achender@kernel.org/
Questions, comments, flames appreciated!
Thanks!
Allison
Gerd Rausch (5):
net/rds: Encode cp_index in TCP source port
net/rds: rds_tcp_conn_path_shutdown must not discard messages
net/rds: Kick-start TCP receiver after accept
net/rds: Use the first lane until RDS_EXTHDR_NPATHS arrives
net/rds: Trigger rds_send_ping() more than once
Håkon Bugge (1):
net/rds: Clear reconnect pending bit
Shamir Rabinovitch (1):
net/rds: new extension header: rdma bytes
net/rds/connection.c | 7 ++-
net/rds/ib_send.c | 19 ++++++-
net/rds/message.c | 66 ++++++++++++++++++-----
net/rds/rds.h | 32 +++++++++---
net/rds/recv.c | 37 +++++++++++--
net/rds/send.c | 118 ++++++++++++++++++++++++++++--------------
net/rds/stats.c | 1 +
net/rds/tcp.c | 1 +
net/rds/tcp.h | 7 ++-
net/rds/tcp_connect.c | 68 +++++++++++++++++++++++-
net/rds/tcp_listen.c | 92 +++++++++++++++++++++++++++++---
net/rds/tcp_recv.c | 4 ++
net/rds/tcp_send.c | 2 +-
13 files changed, 378 insertions(+), 76 deletions(-)
--
2.43.0
next reply other threads:[~2026-01-25 7:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 7:06 Allison Henderson [this message]
2026-01-25 7:06 ` [PATCH net-next v1 1/7] net/rds: new extension header: rdma bytes Allison Henderson
2026-01-26 17:46 ` [net-next,v1,1/7] " Simon Horman
2026-01-27 6:16 ` Allison Henderson
2026-01-25 7:06 ` [PATCH net-next v1 2/7] net/rds: Encode cp_index in TCP source port Allison Henderson
2026-01-25 7:06 ` [PATCH net-next v1 3/7] net/rds: rds_tcp_conn_path_shutdown must not discard messages Allison Henderson
2026-01-25 7:06 ` [PATCH net-next v1 4/7] net/rds: Kick-start TCP receiver after accept Allison Henderson
2026-01-25 7:06 ` [PATCH net-next v1 5/7] net/rds: Clear reconnect pending bit Allison Henderson
2026-01-25 7:06 ` [PATCH net-next v1 6/7] net/rds: Use the first lane until RDS_EXTHDR_NPATHS arrives Allison Henderson
2026-01-25 7:06 ` [PATCH net-next v1 7/7] net/rds: Trigger rds_send_ping() more than once Allison Henderson
2026-01-26 17:47 ` [net-next,v1,7/7] " Simon Horman
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=20260125070651.207042-1-achender@kernel.org \
--to=achender@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.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