netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: akepner@sgi.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] mlx4_core: module param to limit msix vec allocation
Date: Fri, 03 Sep 2010 19:30:46 -0700 (PDT)	[thread overview]
Message-ID: <20100903.193046.184840227.davem@davemloft.net> (raw)
In-Reply-To: <20100903221303.GS2464@sgi.com>

From: Arthur Kepner <akepner@sgi.com>
Date: Fri, 3 Sep 2010 15:13:03 -0700

> On Fri, Sep 03, 2010 at 02:46:58PM -0700, David Miller wrote:
>> No, you really can't do it this way, IRQ allocation management has to
>> be in the kernel.
> 
> Really? I was specifically trying to avoid that, and let the 
> policy about interrupt assignment be done in a user process. 
> 
> Do you have any specific ideas about how that'd look? 

Likely there would be a set of policies just like the cpu
power management layer we have.  And there would be a default,
and userland could override the default.

This also means there would have to be notifications sent to
drivers when the distribution and allocation policy of MSI-X
interrupts is changed.  This is so that, for example, network
drivers can reconfigure their network queues for the new set
of MSI-X vectors available to them after the policy change.

  reply	other threads:[~2010-09-04  2:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-26 17:06 [PATCH] mlx4_core: module param to limit msix vec allocation Arthur Kepner
2010-08-26 19:24 ` David Miller
2010-09-03 20:30   ` Arthur Kepner
2010-09-03 21:46     ` David Miller
2010-09-03 22:13       ` Arthur Kepner
2010-09-04  2:30         ` David Miller [this message]
2010-09-06 17:42           ` Arthur Kepner
2010-09-06 19:51             ` David Miller

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=20100903.193046.184840227.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=akepner@sgi.com \
    --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).