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]
Message-ID: <20070814001441.GN3406@bingen.suse.de>
Date:	Tue, 14 Aug 2007 02:14:41 +0200
From:	Andi Kleen <ak@...e.de>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	Andi Kleen <ak@...e.de>, Christoph Lameter <clameter@....com>,
	Mel Gorman <mel@...net.ie>, Lee.Schermerhorn@...com,
	linux-kernel@...r.kernel.org, linux-mm@...ck.org
Subject: Re: [PATCH 3/4] Embed zone_id information within the zonelist->zones pointer

On Tue, Aug 14, 2007 at 12:22:23AM +0100, Alan Cox wrote:
> > The only tricky part were skbs in a few drivers, but luckily they are only
> > needed for bouncing which can be done without a skb too. For RX it adds
> > one copy, but we can live with that because they're only slow devices.
> 
> Usually found on slow hardware that can't cope with extra copies very
> well.

It's essentially only lance, meth, b44 and bcm43xx and lots of s390.

meth is only used on SGI O2s which are not that slow and unlikely
to work in tree anyways.

b44 and bcm43xx run in fast enough new systems to have no trouble
with copies.

s390 won't change.

That only leaves lance. If it runs in a system with <= 16MB 
of memory is fine. I checked with David if he would consider
adding a second destructor to the skb for this case and he 
said no. Which was an answer which was fine for m.e

So the only systems really affected are lance systems with >16MB.
I don't think we can stop Linux evolution for those sorry. They'll
just have to live with it.

-Andi

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ