From: David Miller <davem@davemloft.net>
To: santosh.shilimkar@oracle.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next][PATCH v3 00/17] net: RDS updates
Date: Tue, 03 Jan 2017 09:46:02 -0500 (EST) [thread overview]
Message-ID: <20170103.094602.1386886488315656207.davem@davemloft.net> (raw)
In-Reply-To: <1483397152-8307-1-git-send-email-santosh.shilimkar@oracle.com>
From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
Date: Mon, 2 Jan 2017 14:45:35 -0800
> v2->v3:
> - Re-based against latest net-next head.
> - Dropped a user visible change after discussing with David Miller.
> It needs some more work to fully support old/new tools matrix.
> - Addressed Dave's comment about bool usage in patch
> "RDS: IB: track and log active side..."
>
> v1->v2:
> Re-aligned indentation in patch 'RDS: mark few internal functions..."
>
> Series consist of:
> - RDMA transport fixes for map failure, listen sequence, handler panic and
> composite message notification.
> - Couple of sparse fixes.
> - Message logging improvements for bind failure, use once mr semantics
> and connection remote address, active end point.
> - Performance improvement for RDMA transport by reducing the post send
> pressure on the queue and spreading the CQ vectors.
> - Useful statistics for socket send/recv usage and receive cache usage.
> - Additional RDS CMSG used by application to track the RDS message
> stages for certain type of traffic to find out latency spots.
> Can be enabled/disabled per socket.
>
> Series generated against 'net-next'. Full patchset is also available on
> below git tree.
...
> git://git.kernel.org/pub/scm/linux/kernel/git/ssantosh/linux.git for_4.11/net-next/rds_v3
Pulled, thanks.
prev parent reply other threads:[~2017-01-03 14:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 22:45 [net-next][PATCH v3 00/17] net: RDS updates Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 01/17] RDS: log the address on bind failure Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 02/17] RDS: mark few internal functions static to make sparse build happy Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 03/17] RDS: IB: include faddr in connection log Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 04/17] RDS: IB: make the transport retry count smallest Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 05/17] RDS: RDMA: fix the ib_map_mr_sg_zbva() argument Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 06/17] RDS: RDMA: start rdma listening after init Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 07/17] RDS: RDMA: return appropriate error on rdma map failures Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 08/17] RDS: IB: split the mr registration and invalidation path Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 09/17] RDS: RDMA: silence the use_once mr log flood Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 10/17] RDS: IB: track and log active side endpoint in connection Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 11/17] RDS: IB: add few useful cache stasts Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 12/17] RDS: IB: Add vector spreading for cqs Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 13/17] RDS: RDMA: Fix the composite message user notification Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 14/17] RDS: IB: fix panic due to handlers running post teardown Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 15/17] RDS: add stat for socket recv memory usage Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 16/17] RDS: make message size limit compliant with spec Santosh Shilimkar
2017-01-02 22:45 ` [net-next][PATCH v3 17/17] RDS: add receive message trace used by application Santosh Shilimkar
2017-01-03 14:46 ` David Miller [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=20170103.094602.1386886488315656207.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=santosh.shilimkar@oracle.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).