All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Allison Henderson <achender@kernel.org>
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
	pabeni@redhat.com, edumazet@google.com, kuba@kernel.org,
	horms@kernel.org
Subject: Re: [PATCH net] net/rds: size a connection's path set by the transport it ends up with
Date: Thu, 24 Sep 2026 17:20:09 +0000	[thread overview]
Message-ID: <179027040953.1664959.5709477689952932392.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260921215027.174657-1-achender@kernel.org>

Hello:

This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Mon, 21 Sep 2026 14:50:27 -0700 you wrote:
> __rds_conn_create() computes npaths from the caller's transport before
> it decides whether a connection to one of the host's own addresses is
> to be handled by the loopback transport instead.  That substitution is
> what an RDS/TCP socket sending to a local address gets, and after it
> the path init loop still runs for the TCP transport's RDS_MPATH_WORKERS
> paths and allocates an ordered workqueue for each, while
> rds_loop_conn_alloc() only ever provides transport data for path 0.
> 
> [...]

Here is the summary with links:
  - [net] net/rds: size a connection's path set by the transport it ends up with
    https://git.kernel.org/netdev/net/c/ba3d1f480c7a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2026-09-24 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-21 21:50 [PATCH net] net/rds: size a connection's path set by the transport it ends up with Allison Henderson
2026-09-21 21:59 ` sashiko-bot
2026-09-24 17:20 ` patchwork-bot+netdevbpf [this message]

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=179027040953.1664959.5709477689952932392.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=achender@kernel.org \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.