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 15:13:03 -0700 [thread overview]
Message-ID: <20100903221303.GS2464@sgi.com> (raw)
In-Reply-To: <20100903.144658.149830788.davem@davemloft.net>
On Fri, Sep 03, 2010 at 02:46:58PM -0700, David Miller wrote:
> From: Arthur Kepner <akepner@sgi.com>
> Date: Fri, 3 Sep 2010 13:30:44 -0700
>
> > I have that running on a (very small) system and it seems to
> > work OK. Will send out the patch in just a minute.
>
> Failure vs. non-failure of allocation of a kernel managed physical
> resource can't be determined by a userland process which may or may
> not be running.
But even if there's no user process running, it's no worse
than what we've got now.
>
> In fact, if I build all of my drivers built-in and use NFS root which
> will activate and bring up network devices, userland won't even be
> present when the interrupts are requested.
Yep. This only works once the user-level irq balancer is
available.
>
> 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?
--
Arthur
next prev parent reply other threads:[~2010-09-03 22:13 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 [this message]
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=20100903221303.GS2464@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 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).