From: Tony Lu <tonylu@linux.alibaba.com>
To: Wenjia Zhang <wenjia@linux.ibm.com>
Cc: David Miller <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
netdev@vger.kernel.org, linux-s390@vger.kernel.org,
Heiko Carstens <hca@linux.ibm.com>,
Karsten Graul <kgraul@linux.ibm.com>,
Alexandra Winter <wintera@linux.ibm.com>,
Stefan Raspl <raspl@linux.ibm.com>
Subject: Re: [PATCH net-next 0/4] net/smc: updates 2022-7-25
Date: Tue, 26 Jul 2022 11:31:26 +0800 [thread overview]
Message-ID: <Yt9gDrS6Ag0Bd9id@TonyMac-Alibaba> (raw)
In-Reply-To: <20220725141000.70347-1-wenjia@linux.ibm.com>
On Mon, Jul 25, 2022 at 04:09:56PM +0200, Wenjia Zhang wrote:
> Hi Dave & Jakub,
>
> please apply the following patches to netdev's net-next tree.
>
> These patches do some preparation to make ISM available for uses beyond
> SMC-D, and a bunch of cleanups.
>
> Thanks,
> Wenjia
Hello Wenjia,
Making ISM available for others sounds great. I proposed a RFC [1] last
week. The RFC brings an ISM-like device to accelerate inter-VM scenario.
I am wondering the plan about this, which may help us. And hope to hear
from you about the RFC [1]. Thank you.
[1] https://lore.kernel.org/all/20220720170048.20806-1-tonylu@linux.alibaba.com/
Cheers,
Tony Lu
next prev parent reply other threads:[~2022-07-26 3:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 14:09 [PATCH net-next 0/4] net/smc: updates 2022-7-25 Wenjia Zhang
2022-07-25 14:09 ` [PATCH net-next 1/4] net/smc: Eliminate struct smc_ism_position Wenjia Zhang
2022-07-26 2:48 ` Tony Lu
2022-07-25 14:09 ` [PATCH net-next 2/4] s390/ism: Cleanups Wenjia Zhang
2022-07-26 3:13 ` Tony Lu
2022-07-25 14:09 ` [PATCH net-next 3/4] net/smc: Pass on DMBE bit mask in IRQ handler Wenjia Zhang
2022-07-26 3:11 ` Tony Lu
2022-07-25 14:10 ` [PATCH net-next 4/4] net/smc: Enable module load on netlink usage Wenjia Zhang
2022-07-26 2:54 ` Tony Lu
2022-07-26 3:31 ` Tony Lu [this message]
2022-07-26 8:02 ` [PATCH net-next 0/4] net/smc: updates 2022-7-25 Wenjia Zhang
2022-07-27 12:30 ` patchwork-bot+netdevbpf
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=Yt9gDrS6Ag0Bd9id@TonyMac-Alibaba \
--to=tonylu@linux.alibaba.com \
--cc=davem@davemloft.net \
--cc=hca@linux.ibm.com \
--cc=kgraul@linux.ibm.com \
--cc=kuba@kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raspl@linux.ibm.com \
--cc=wenjia@linux.ibm.com \
--cc=wintera@linux.ibm.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;
as well as URLs for NNTP newsgroup(s).