From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
To: netdev@vger.kernel.org, davem@davemloft.net
Cc: linux-kernel@vger.kernel.org
Subject: RDS: Major clean-up with couple of new features for 4.6
Date: Tue, 1 Mar 2016 15:20:41 -0800 [thread overview]
Message-ID: <1456874454-10355-1-git-send-email-santosh.shilimkar@oracle.com> (raw)
v3:
Re-generated the same series by omitting "-D" option from git format-patch
command. Since first patch has file removals, git apply/am can't deal
with it when formated with '-D' option.
v2:
Dropped module parameter from [PATCH 11/13] as suggested by David Miller
Series is generated against net-next but also applies against Linus's tip
cleanly. Entire patchset is available at below git tree:
git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux.git for_4.6/net-next/rds_v2
The diff-stat looks bit scary since almost ~4K lines of code is
getting removed. Brief summary of the series:
- Drop the stale iWARP support:
RDS iWarp support code has become stale and non testable for
sometime. As discussed and agreed earlier on list, am dropping
its support for good. If new iWarp user(s) shows up in future,
the plan is to adapt existing IB RDMA with special sink case.
- RDS gets SO_TIMESTAMP support
- Long due RDS maintainer entry gets updated
- Some RDS IB code refactoring towards new FastReg Memory registration (FRMR)
- Lastly the initial support for FRMR
RDS IB RDMA performance with FRMR is not yet as good as FMR and I do have
some patches in progress to address that. But they are not ready for 4.6
so I left them out of this series.
Also am keeping eye on new CQ API adaptations like other ULPs doing and
will try to adapt RDS for the same most likely in 4.7+ timeframe.
Santosh Shilimkar (12):
RDS: Drop stale iWARP RDMA transport
RDS: Add support for SO_TIMESTAMP for incoming messages
MAINTAINERS: update RDS entry
RDS: IB: Remove the RDS_IB_SEND_OP dependency
RDS: IB: Re-organise ibmr code
RDS: IB: create struct rds_ib_fmr
RDS: IB: move FMR code to its own file
RDS: IB: add connection info to ibmr
RDS: IB: handle the RDMA CM time wait event
RDS: IB: add mr reused stats
RDS: IB: add Fastreg MR (FRMR) detection support
RDS: IB: allocate extra space on queues for FRMR support
Avinash Repaka (1):
RDS: IB: Support Fastreg MR (FRMR) memory registration mode
Documentation/networking/rds.txt | 4 +-
MAINTAINERS | 6 +-
net/rds/Kconfig | 7 +-
net/rds/Makefile | 4 +-
net/rds/af_rds.c | 26 ++
net/rds/ib.c | 47 +-
net/rds/ib.h | 37 +-
net/rds/ib_cm.c | 59 ++-
net/rds/ib_fmr.c | 248 ++++++++++
net/rds/ib_frmr.c | 376 +++++++++++++++
net/rds/ib_mr.h | 148 ++++++
net/rds/ib_rdma.c | 495 ++++++--------------
net/rds/ib_send.c | 6 +-
net/rds/ib_stats.c | 2 +
net/rds/iw.c | 312 -------------
net/rds/iw.h | 398 ----------------
net/rds/iw_cm.c | 769 ------------------------------
net/rds/iw_rdma.c | 837 ---------------------------------
net/rds/iw_recv.c | 904 ------------------------------------
net/rds/iw_ring.c | 169 -------
net/rds/iw_send.c | 981 ---------------------------------------
net/rds/iw_stats.c | 95 ----
net/rds/iw_sysctl.c | 123 -----
net/rds/rdma_transport.c | 21 +-
net/rds/rdma_transport.h | 5 -
net/rds/rds.h | 1 +
net/rds/recv.c | 20 +-
27 files changed, 1065 insertions(+), 5035 deletions(-)
create mode 100644 net/rds/ib_fmr.c
create mode 100644 net/rds/ib_frmr.c
create mode 100644 net/rds/ib_mr.h
delete mode 100644 net/rds/iw.c
delete mode 100644 net/rds/iw.h
delete mode 100644 net/rds/iw_cm.c
delete mode 100644 net/rds/iw_rdma.c
delete mode 100644 net/rds/iw_recv.c
delete mode 100644 net/rds/iw_ring.c
delete mode 100644 net/rds/iw_send.c
delete mode 100644 net/rds/iw_stats.c
delete mode 100644 net/rds/iw_sysctl.c
--
1.9.1
next reply other threads:[~2016-03-01 23:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-01 23:20 Santosh Shilimkar [this message]
2016-03-01 23:20 ` [net-next][PATCH v3 01/13] RDS: Drop stale iWARP RDMA transport Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 02/13] RDS: Add support for SO_TIMESTAMP for incoming messages Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 03/13] MAINTAINERS: update RDS entry Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 04/13] RDS: IB: Remove the RDS_IB_SEND_OP dependency Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 05/13] RDS: IB: Re-organise ibmr code Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 06/13] RDS: IB: create struct rds_ib_fmr Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 07/13] RDS: IB: move FMR code to its own file Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 08/13] RDS: IB: add connection info to ibmr Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 09/13] RDS: IB: handle the RDMA CM time wait event Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 10/13] RDS: IB: add mr reused stats Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 11/13] RDS: IB: add Fastreg MR (FRMR) detection support Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 12/13] RDS: IB: allocate extra space on queues for FRMR support Santosh Shilimkar
2016-03-01 23:20 ` [net-next][PATCH v3 13/13] RDS: IB: Support Fastreg MR (FRMR) memory registration mode Santosh Shilimkar
2016-03-02 19:13 ` RDS: Major clean-up with couple of new features for 4.6 David Miller
2016-03-02 19:15 ` santosh shilimkar
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=1456874454-10355-1-git-send-email-santosh.shilimkar@oracle.com \
--to=santosh.shilimkar@oracle.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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).