linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "santosh.shilimkar@oracle.com" <santosh.shilimkar@oracle.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	ssantosh@kernel.org
Subject: Re: [PATCH v3 00/14] RDS: connection scalability and performance improvements
Date: Wed, 7 Oct 2015 08:58:32 -0700	[thread overview]
Message-ID: <56154128.2010309@oracle.com> (raw)
In-Reply-To: <20151007.021634.1127057852275250731.davem@davemloft.net>

On 10/7/15 2:16 AM, David Miller wrote:
> From: Santosh Shilimkar <santosh.shilimkar@oracle.com>
> Date: Mon,  5 Oct 2015 10:56:23 -0700
>
>> [v3]
>> Updated patch "[PATCH v2 05/14] RDS: defer the over_batch work to
>> send worker" as per David Miller's comment [4] to avoid the magic
>> value usage. Patch now makes use of already available but unused
>> send_batch_count module parameter. Rest of the patches are same as
>> earlier version v2 [3]
>
> Can you respin this again?  Your repost of patch 05/14 was severely whitespace
> damaged.
>
Sorry about that. I thought mailer won't eat tabs but it did. Just sent
the series again. Bumped up the version to v4 from archives perspective.

Thanks !!

Regards,
Santosh

      reply	other threads:[~2015-10-07 15:58 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-05 17:56 [PATCH v3 00/14] RDS: connection scalability and performance improvements Santosh Shilimkar
2015-10-05 17:56 ` [PATCH v3 01/14] RDS: use kfree_rcu in rds_ib_remove_ipaddr Santosh Shilimkar
2015-10-05 17:56 ` [PATCH v3 02/14] RDS: make socket bind/release locking scheme simple and more efficient Santosh Shilimkar
2015-10-05 17:56 ` [PATCH v3 03/14] RDS: fix rds_sock reference bug while doing bind Santosh Shilimkar
2015-10-05 17:56 ` [PATCH v3 04/14] RDS: Use per-bucket rw lock for bind hash-table Santosh Shilimkar
2015-10-05 17:56 ` [PATCH v3 05/14] RDS: defer the over_batch work to send worker Santosh Shilimkar
2015-10-05 18:31   ` santosh shilimkar
2015-10-05 17:56 ` [PATCH v3 06/14] RDS: use rds_send_xmit() state instead of RDS_LL_SEND_FULL Santosh Shilimkar
2015-10-05 17:56 ` [PATCH v3 07/14] RDS: IB: ack more receive completions to improve performance Santosh Shilimkar
2015-10-05 17:56 ` [PATCH v3 08/14] RDS: IB: split send completion handling and do batch ack Santosh Shilimkar
2015-10-05 17:56 ` [PATCH v3 09/14] RDS: IB: handle rds_ibdev release case instead of crashing the kernel Santosh Shilimkar
2015-10-05 17:56 ` [PATCH v3 10/14] RDS: IB: fix the rds_ib_fmr_wq kick call Santosh Shilimkar
2015-10-05 17:56 ` [PATCH v3 11/14] RDS: IB: use already available pool handle from ibmr Santosh Shilimkar
2015-10-05 17:56 ` [PATCH v3 12/14] RDS: IB: mark rds_ib_fmr_wq static Santosh Shilimkar
2015-10-05 17:56 ` [PATCH v3 13/14] RDS: IB: use max_mr from HCA caps than max_fmr Santosh Shilimkar
2015-10-05 17:56 ` [PATCH v3 14/14] RDS: IB: split mr pool to improve 8K messages performance Santosh Shilimkar
2015-10-07  9:16 ` [PATCH v3 00/14] RDS: connection scalability and performance improvements David Miller
2015-10-07 15:58   ` santosh.shilimkar [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=56154128.2010309@oracle.com \
    --to=santosh.shilimkar@oracle.com \
    --cc=davem@davemloft.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=ssantosh@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).