netdev - Re: [PATCH] mlx4_core: module param to limit msix vec allocation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20100903.144658.149830788.davem@davemloft.net>
Date:	Fri, 03 Sep 2010 14:46:58 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	akepner@....com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] mlx4_core: module param to limit msix vec allocation

From: Arthur Kepner <akepner@....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.

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.

No, you really can't do it this way, IRQ allocation management has to
be in the kernel.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html