All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arthur Kepner <akepner@sgi.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] mlx4_core: module param to limit msix vec allocation
Date: Fri, 3 Sep 2010 13:30:44 -0700	[thread overview]
Message-ID: <20100903203044.GN2464@sgi.com> (raw)
In-Reply-To: <20100826.122407.260097270.davem@davemloft.net>

On Thu, Aug 26, 2010 at 12:24:07PM -0700, David Miller wrote:
> ....
> And what the heck happens if every single device driver tries to
> handle this problem in the same way?  It makes no sense to make
> the user specify N special module parameters just to get a working
> system using MSI-X.
> 
> This must be fixed in a centralized way that allows coordination
> between devices which compete for MSI-X vector resources, rather than
> in a way that is specific to each and every device type.
> 

OK, how about this. Each time the kernel assigns a default 
affinity for an interrupt, it generates a netlink message, 
and a user-level interrupt balancer can decide whether and 
how to reassign the interrupt? 

I have that running on a (very small) system and it seems to 
work OK. Will send out the patch in just a minute.

-- 
Arthur

  reply	other threads:[~2010-09-03 20: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 [this message]
2010-09-03 21:46     ` David Miller
2010-09-03 22:13       ` Arthur Kepner
2010-09-04  2:30         ` David Miller
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=20100903203044.GN2464@sgi.com \
    --to=akepner@sgi.com \
    --cc=davem@davemloft.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.