linux-kernel - Re: [PATCH] add pci revision id to struct pci

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: <1162823699.1566.86.camel@localhost.localdomain>
Date:	Mon, 06 Nov 2006 14:34:58 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Arjan van de Ven <arjan@...radead.org>
Cc:	Conke Hu <conke.hu@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] add pci revision id to struct pci_dev

Ar Llu, 2006-11-06 am 15:19 +0100, ysgrifennodd Arjan van de Ven:
> store it in the pci device struct, it's a very logical thing esp since
> the pci device/vendor ids are stored there too (and those you can also
> read from the hw if you want ;)

We need those cached because we iterate them on every PCI device match
and that is both regularly accessed and performance relevant. We also
need to cache them for the removed device case, unlike revision id.

> 
-
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/