linux-kernel - RE: [char-misc-next 07/15] mei: use wrietl/readl instead of io wrappers

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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 4 Dec 2012 16:02:17 +0000
From:	"Winkler, Tomas" <tomas.winkler@...el.com>
To:	Alan Cox <alan@...ux.intel.com>,
	"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>
CC:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	"arnd@...db.de" <arnd@...db.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Stanislaw Gruszka <sgruszka@...hat.com>
Subject: RE: [char-misc-next 07/15] mei: use wrietl/readl instead of io
 wrappers

> > > As to overhead. I'd love to see a measurement that can detect the
> > > difference. Do you have a benchmark that shows it ?
> >
> > Don't have any numbers but it seems reasonable to me.
> 
> Processors are pretty good at prediction these days. I've not seen any
> evidence to support the assumption.

I don't have strong opinion about it, yet what would be benefit of keeping the io abstraction layer,
In case we are sure it is not used with io ports?

Anyhow If time permits I will try to run the stress again. 

Greg, can you pleased just drop this patch for now, I don't believe it creates any conflict. 

Thanks
Tomas



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