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: <20081116.002155.74280893.davem@davemloft.net>
Date:	Sun, 16 Nov 2008 00:21:55 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	akpm@...ux-foundation.org
Cc:	arjan@...radead.org, laijs@...fujitsu.com, menage@...gle.com,
	kamezawa.hiroyu@...fujitsu.com, balbir@...ux.vnet.ibm.com,
	jens.axboe@...cle.com, jack@...e.cz, jes@....com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/7] mm: introduce simple_malloc()/simple_free()

From: Andrew Morton <akpm@...ux-foundation.org>
Date: Sat, 15 Nov 2008 21:03:34 -0800

> On Sat, 15 Nov 2008 20:52:29 -0800 Arjan van de Ven <arjan@...radead.org> wrote:
> 
> > Realistically, people should try hard
> > to use small datastructure instead....
> 
> Yup, it makes it easier for people to do something which we strongly
> discourage.  The risk got worse with all these 64-bit machines with
> vast amounts of virtual address space.  It makes it easier for people
> to develop and "test" code which isn't reliable on smaller machines.

I don't see it as being used for common operations (unlike vmap BTW,
which XFS does like crazy).  It's mainly for core hash tables and
similarly large structures.  And also, for those things, the NUMA
spreading helps.

And, in any event, for those cases:

1) we are already doing this exact thing

2) due to #1 we have N copies of the same damn code

So whatever policy fits your fancy, wouldn't it be better to "enforce"
this in one spot instead of the 12 copies we have already?

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