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]
Date:	Mon, 21 Mar 2016 11:59:25 -0500 (CDT)
From:	Christoph Lameter <cl@...ux.com>
To:	"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Alexander Viro <viro@...iv.linux.org.uk>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Matthew Wilcox <willy@...ux.intel.com>,
	Hugh Dickins <hughd@...gle.com>, linux-kernel@...r.kernel.org,
	linux-mm@...ck.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 0/3] fs, mm: get rid of PAGE_CACHE_* and page_cache_{get,release}
 macros

On Mon, 21 Mar 2016, Kirill A. Shutemov wrote:

> We do have anon-THP pages on LRU. My huge tmpfs patchset also put
> file-THPs on LRU list.

So they are on the LRU as 4k units? Tried to look it up.

> > Will this actually work if we have really huge memory (100s of TB) where
> > almost everything is a huge page? Guess we have to use hugetlbfs and we
> > need to think about this as being exempt from paging.
>
> Sorry, I failed to understand your message.
>
> Look on huge tmpfs patchset. It allows both small and huge pages in page
> cache.

Thus my wonder about this patchset. It seems then that the huge pages are
treated as 4k pages? Otherwise we would have two sizes for pages in the
page cache. Sorry I did not follow that too closely. Will try finding that
patchset.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ