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: <20090529160607.db4d55b6.kamezawa.hiroyu@jp.fujitsu.com>
Date:	Fri, 29 May 2009 16:06:07 +0900
From:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
To:	KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Cc:	Christoph Pleger <Christoph.Pleger@...tu-dortmund.de>,
	linux-kernel@...r.kernel.org
Subject: Re: Maximum size of a swap partition

On Fri, 29 May 2009 15:47:01 +0900
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com> wrote:


> I'm not sure whether there are other limitations. But maybe enough big.
> 
I missed the another story.

For managing swap, the kernel uses 2bytes per 1 swap entry.
Then, if swap parttion is 1Gbytes, the kernel uses 512k bytes of memory.

in x86, this memory is allocated from vmalloc() area (you can see it in meminfo)
and it has only 80?MB. And there are other users of this area.

Then, in real x86-32bit world, you can't use verrrrry big swap device.

Then, 16GB=8MB in the kernel (or some more) is realistic limitation for usual
users.

Thanks,
-Kame

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