linux-kernel - RE: [PATCH RFC 00/77] Re-design MSI/MSI-X interrupts enablement pattern

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: <AE90C24D6B3A694183C094C60CF0A2F6026B7371@saturn3.aculab.com>
Date:	Fri, 4 Oct 2013 09:31:49 +0100
From:	"David Laight" <David.Laight@...LAB.COM>
To:	"Alexander Gordeev" <agordeev@...hat.com>,
	"Ben Hutchings" <bhutchings@...arflare.com>
Cc:	<linux-mips@...ux-mips.org>,
	"VMware, Inc." <pv-drivers@...are.com>,
	<linux-nvme@...ts.infradead.org>, <linux-ide@...r.kernel.org>,
	<linux-s390@...r.kernel.org>, "Andy King" <acking@...are.com>,
	<linux-scsi@...r.kernel.org>, <linux-rdma@...r.kernel.org>,
	<x86@...nel.org>, "Ingo Molnar" <mingo@...hat.com>,
	<linux-pci@...r.kernel.org>, <iss_storagedev@...com>,
	<linux-driver@...gic.com>, "Tejun Heo" <tj@...nel.org>,
	"Bjorn Helgaas" <bhelgaas@...gle.com>,
	"Dan Williams" <dan.j.williams@...el.com>,
	"Jon Mason" <jon.mason@...el.com>,
	"Solarflare linux maintainers" <linux-net-drivers@...arflare.com>,
	<netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	"Ralf Baechle" <ralf@...ux-mips.org>,
	<e1000-devel@...ts.sourceforge.net>,
	"Martin Schwidefsky" <schwidefsky@...ibm.com>,
	<linux390@...ibm.com>, <linuxppc-dev@...ts.ozlabs.org>
Subject: RE: [PATCH RFC 00/77] Re-design MSI/MSI-X interrupts enablement pattern

> > It seems to me that a more useful interface would take a minimum and
> > maximum number of vectors from the driver.  This wouldn't allow the
> > driver to specify that it could only accept, say, any even number within
> > a certain range, but you could still leave the current functions
> > available for any driver that needs that.
> 
> Mmmm.. I am not sure I am getting it. Could you please rephrase?

One possibility is for drivers than can use a lot of interrupts to
request a minimum number initially and then request the additional
ones much later on.
That would make it less likely that none will be available for
devices/drivers that need them but are initialised later.

	David



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/