From: Karsten Graul <kgraul@linux.ibm.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, linux-s390@vger.kernel.org,
heiko.carstens@de.ibm.com, raspl@linux.ibm.com,
ubraun@linux.ibm.com
Subject: [PATCH net-next 00/13] net/smc: add and delete link processing
Date: Sat, 2 May 2020 14:35:39 +0200 [thread overview]
Message-ID: <20200502123552.17204-1-kgraul@linux.ibm.com> (raw)
These patches add the 'add link' and 'delete link' processing as
SMC server and client. This processing allows to establish and
remove links of a link group dynamically.
They are based on the patches I sent yesterday, I cannot see yesterdays
patches in the net-next git tree yet.
Karsten Graul (13):
net/smc: first part of add link processing as SMC client
net/smc: rkey processing for a new link as SMC client
net/smc: final part of add link processing as SMC client
net/smc: first part of add link processing as SMC server
net/smc: rkey processing for a new link as SMC server
net/smc: final part of add link processing as SMC server
net/smc: delete an asymmetric link as SMC server
net/smc: activate SMC server add link functions
net/smc: llc_del_link_work and use the LLC flow for delete link
net/smc: delete link processing as SMC client
net/smc: delete link processing as SMC server
net/smc: enqueue local LLC messages
net/smc: save state of last sent CDC message
net/smc/af_smc.c | 4 +-
net/smc/smc.h | 4 +
net/smc/smc_cdc.c | 6 +
net/smc/smc_core.c | 29 +-
net/smc/smc_core.h | 4 +-
net/smc/smc_llc.c | 774 +++++++++++++++++++++++++++++++++++++++++++--
net/smc/smc_llc.h | 5 +
net/smc/smc_wr.c | 2 +-
net/smc/smc_wr.h | 1 +
9 files changed, 786 insertions(+), 43 deletions(-)
--
2.17.1
next reply other threads:[~2020-05-02 12:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-02 12:35 Karsten Graul [this message]
2020-05-02 12:35 ` [PATCH net-next 01/13] net/smc: first part of add link processing as SMC client Karsten Graul
2020-05-02 23:38 ` David Miller
2020-05-02 12:35 ` [PATCH net-next 02/13] net/smc: rkey processing for a new link " Karsten Graul
2020-05-02 12:35 ` [PATCH net-next 03/13] net/smc: final part of add link processing " Karsten Graul
2020-05-02 12:35 ` [PATCH net-next 04/13] net/smc: first part of add link processing as SMC server Karsten Graul
2020-05-02 12:35 ` [PATCH net-next 05/13] net/smc: rkey processing for a new link " Karsten Graul
2020-05-02 12:35 ` [PATCH net-next 06/13] net/smc: final part of add link processing " Karsten Graul
2020-05-02 12:35 ` [PATCH net-next 07/13] net/smc: delete an asymmetric link " Karsten Graul
2020-05-02 12:35 ` [PATCH net-next 08/13] net/smc: activate SMC server add link functions Karsten Graul
2020-05-02 12:35 ` [PATCH net-next 09/13] net/smc: llc_del_link_work and use the LLC flow for delete link Karsten Graul
2020-05-02 12:35 ` [PATCH net-next 10/13] net/smc: delete link processing as SMC client Karsten Graul
2020-05-02 12:35 ` [PATCH net-next 11/13] net/smc: delete link processing as SMC server Karsten Graul
2020-05-02 12:35 ` [PATCH net-next 12/13] net/smc: enqueue local LLC messages Karsten Graul
2020-05-02 12:35 ` [PATCH net-next 13/13] net/smc: save state of last sent CDC message Karsten Graul
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=20200502123552.17204-1-kgraul@linux.ibm.com \
--to=kgraul@linux.ibm.com \
--cc=davem@davemloft.net \
--cc=heiko.carstens@de.ibm.com \
--cc=linux-s390@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=raspl@linux.ibm.com \
--cc=ubraun@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).