linux-kernel - Re: Allow setting of number of raw devices as a module parameter

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: <20110503104258.5a808b9d@lxorguk.ukuu.org.uk>
Date:	Tue, 3 May 2011 10:42:58 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Jan Kara <jack@...e.cz>
Cc:	Greg KH <gregkh@...e.de>,
	Andrew Morton <akpm@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Allow setting of number of raw devices as a module parameter

> So if people don't like vmalloc() (which I can understand), then I see no
> other option than dynamically allocating struct raw_device_data.

That gets rather more complicated.

So yes I agree your question is a good one - for smaller sizes I'd rather
see it from the kmalloc/static pool but for small sizes it also doesn't
matter much anyway.

Objection rescinded - I think you've proved convincingly that the only
way to sort it properly is horribly complicated
--
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/