[lkml]   [2002]   [Aug]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: aio-core why not using SuS? [Re: [rfc] aio-core for 2.5.29 (Re: async-io API registration for 2.5.29)]

On Thu, 15 Aug 2002, Linus Torvalds wrote:
> My bet is that we'll never do it due to performance issues. It's just
> simpler to make the high pages end up being some special stuff (ie the old
> "swap victim cache" etc that wouldn't show up to the VM proper).

Actually, the simplest schenario is to just make an arbitrary cut-off at
8G or 16G of RAM, and make anything above it default to the hugetlb zone,
and make that use a separate hugetlb map which does refcounts at 2MB
granularity). And create fake "struct page" entries for those things that
have to have it, along with a separate kmap area that holds a few of the
big mappings.

There's an almost complete overlap between people who want hugetlb and
64GB x86 machines anyway, so I doubt you'd find people to complain.

And the advantage of the hugetlb stuff is exactly the fact that the normal
VM doesn't need to worry about it. It's nonswappable, and doesn't get IO
done into it through any of the normal paths.

Minimal impact.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.158 / U:0.680 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site