public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Sreedhar Kodali <srkodali-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>
To: Bart Van Assche <bvanassche-HInyCGIudOg@public.gmane.org>
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
	pradeeps-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org,
	linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH v2 3/4] rsockets: distribute completion queue vectors among multiple cores
Date: Thu, 11 Sep 2014 18:04:43 +0530	[thread overview]
Message-ID: <ef556922e7b766360a38df904dff1c70@imap.linux.ibm.com> (raw)
In-Reply-To: <edc2b05703209d2a7626a31abb170ceb-FJGp5E75HVmZamtmwQBW5tBPR1lH4CV8@public.gmane.org>

On 2014-09-09 17:58, Sreedhar Kodali wrote:
> On 2014-09-08 23:52, Bart Van Assche wrote:
>> On 09/08/14 16:27, Sreedhar Kodali wrote:
>>> Thanks for your insights.  Your suggestion of having a separate
>>> vector per process is really useful when multiple processes are
>>> simultaneously running in the same environment.  At the 
>>> implementation
>>> level this requires an extended configuration file format. Can't
>>> we possibly think of this as a next iteration?
>> 
>> This patch introduces a new configuration file
>> (/etc/rdma/rsocket/comp_vector). User expect that such configuration
>> files remain supported after a software upgrade. In other words,
>> introduction of a new configuration file deserves careful
>> consideration. Do we really need this new configuration file ? Why not
>> e.g. to change the default behavior of the rsockets library into
>> spreading the interrupt processing workload over all completion
>> vectors supported by the HCA ? Furthermore, the number of completion
>> vectors that is supported by an HCA not only depends on the HCA
>> firmware but also on the number of completion vectors a HCA could
>> allocate during driver initialization. The number of MSI-X vectors
>> available on an x86-64 system is limited (224). Dual-socket x86-64
>> motherboards with up to 11 PCIe slots are available commercially. If
>> all PCIe-slots are populated it's almost sure that one of the PCIe
>> cards won't be assigned as many MSI-X vectors as it could use.
>> 
>> Sorry but I'm not convinced that using the same completion vector mask
>> for all HCA's and all processes is a good idea. Or is there perhaps
>> something I have overlooked ?
>> 
>> Bart.
> 
> Hi Bart,
> 
> I agree with your suggestions - working on the revised patch 
> accordingly.
> 
> Thank You.
> 
> - Sreedhar
> 

Hi Bart,

I have sent the revised patch v4 that groups and assigns comp vectors 
per process as you suggested.  Please go through it.

Thank You.

- Sreedhar
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" 
> in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2014-09-11 12:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-05 13:18 [PATCH v2 3/4] rsockets: distribute completion queue vectors among multiple cores Sreedhar Kodali
     [not found] ` <f028f54b9900ee34fcd1abd1d90d10e6-FJGp5E75HVmZamtmwQBW5tBPR1lH4CV8@public.gmane.org>
2014-09-05 15:47   ` Bart Van Assche
     [not found]     ` <5409DB0D.6080103-HInyCGIudOg@public.gmane.org>
2014-09-06  3:06       ` Sreedhar Kodali
     [not found]         ` <850a2835b5917f6da62af3d1ea0288fd-FJGp5E75HVmZamtmwQBW5tBPR1lH4CV8@public.gmane.org>
2014-09-08  6:47           ` Bart Van Assche
     [not found]             ` <540D50E9.5050709-HInyCGIudOg@public.gmane.org>
2014-09-08 14:27               ` Sreedhar Kodali
     [not found]                 ` <a8ac21f3c9d7c802ab089bc0d432e40b-FJGp5E75HVmZamtmwQBW5tBPR1lH4CV8@public.gmane.org>
2014-09-08 18:22                   ` Bart Van Assche
     [not found]                     ` <540DF3CC.1060304-HInyCGIudOg@public.gmane.org>
2014-09-09 12:28                       ` Sreedhar Kodali
     [not found]                         ` <edc2b05703209d2a7626a31abb170ceb-FJGp5E75HVmZamtmwQBW5tBPR1lH4CV8@public.gmane.org>
2014-09-11 12:34                           ` Sreedhar Kodali [this message]
     [not found]                             ` <ef556922e7b766360a38df904dff1c70-FJGp5E75HVmZamtmwQBW5tBPR1lH4CV8@public.gmane.org>
2014-09-15  9:06                               ` Bart Van Assche
     [not found]                                 ` <5416ABFB.7040701-HInyCGIudOg@public.gmane.org>
2014-09-16  4:33                                   ` Sreedhar Kodali
     [not found]                                     ` <d5804c38cb47bcc79eb3962cf8ca6989-FJGp5E75HVmZamtmwQBW5tBPR1lH4CV8@public.gmane.org>
2014-09-16  4:57                                       ` Hefty, Sean
     [not found]                                         ` <1828884A29C6694DAF28B7E6B8A8237399DD3DA8-P5GAC/sN6hkd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-09-17  5:54                                           ` Sreedhar Kodali

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=ef556922e7b766360a38df904dff1c70@imap.linux.ibm.com \
    --to=srkodali-23vcf4htsmix0ybbhkvfkdbpr1lh4cv8@public.gmane.org \
    --cc=bvanassche-HInyCGIudOg@public.gmane.org \
    --cc=linux-rdma-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=pradeeps-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
    --cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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