From: Karsten Graul <kgraul@linux.ibm.com>
To: Tony Lu <tonylu@linux.alibaba.com>
Cc: kuba@kernel.org, davem@davemloft.net, guwen@linux.alibaba.com,
netdev@vger.kernel.org, linux-s390@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH RFC net-next] net/smc: Unbind buffer size from clcsock and make it tunable
Date: Tue, 23 Nov 2021 10:33:07 +0100 [thread overview]
Message-ID: <9aaa03b2-4478-6dff-0bfc-06eba7ef2bf7@linux.ibm.com> (raw)
In-Reply-To: <YZyQg23Vqes4Ls5t@TonyMac-Alibaba>
On 23/11/2021 07:56, Tony Lu wrote:
> To solve this issue, we developed a set of patches to replace the
> AF_INET / SOCK_STREAM with AF_SMC / SMCPROTO_SMC{6} by configuration.
> So that we can control acceleration in kernel without any other changes
> in user-space, and won't break our application containers and publish
> workflow. These patches are still improving for upstream.
This sounds interesting. Will this also be namespace-based like the sysctls
in the current patch? Will this future change integrate nicely with the current
new sysctls? This might allow to activate smc for containers, selectively.
Please send these changes in a patch series together when they are finished.
We would like to review them as a whole to see how things play together.
Thank you!
next prev parent reply other threads:[~2021-11-23 9:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-22 13:42 [PATCH RFC net-next] net/smc: Unbind buffer size from clcsock and make it tunable Tony Lu
2021-11-22 15:08 ` Karsten Graul
2021-11-23 6:56 ` Tony Lu
2021-11-23 9:33 ` Karsten Graul [this message]
2021-11-24 4:46 ` Tony Lu
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=9aaa03b2-4478-6dff-0bfc-06eba7ef2bf7@linux.ibm.com \
--to=kgraul@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=guwen@linux.alibaba.com \
--cc=kuba@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tonylu@linux.alibaba.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