From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Hugh Dickins <hugh@veritas.com>
Cc: Adam Litke <agl@us.ibm.com>,
Christoph Hellwig <hch@infradead.org>,
linux-mm@kvack.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Hugetlb demotion for x86
Date: Thu, 11 May 2006 16:33:49 +0100 [thread overview]
Message-ID: <1147361629.26130.32.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0605111607250.24407@blonde.wat.veritas.com>
On Iau, 2006-05-11 at 16:15 +0100, Hugh Dickins wrote:
> > For one: an application using lots of private huge pages should not be
> > prohibited from forking if it's likely to just exec a small helper
> > program.
>
> This is an excellent use for madvise(start, length, MADV_DONTFORK).
> Though it was added mainly for RDMA issues, it's a great way for a
> program with a huge commitment to exclude areas of its address space
> from the fork, so making that fork much more likely to succeed.
Or fork using vfork() in that case which has even more wins and is a
more efficient if more hair-raising way of doing it
next prev parent reply other threads:[~2006-05-11 15:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 18:56 [RFC] Hugetlb demotion for x86 Adam Litke
2006-05-10 19:46 ` Dave Hansen
2006-05-10 19:49 ` Dave Hansen
2006-05-10 20:05 ` Christoph Hellwig
2006-05-10 20:32 ` Adam Litke
2006-05-10 20:49 ` Christoph Hellwig
2006-05-10 21:45 ` Adam Litke
2006-05-11 15:15 ` Hugh Dickins
2006-05-11 15:33 ` Alan Cox [this message]
2006-05-11 15:59 ` Adam Litke
2006-05-10 21:38 ` Andi Kleen
2006-05-10 23:42 ` Christoph Lameter
2006-05-10 23:42 ` Christoph Lameter
2006-05-11 16:10 ` Adam Litke
2006-05-15 14:20 ` Dave Hansen
2006-05-15 14:20 ` Dave Hansen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1147361629.26130.32.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=agl@us.ibm.com \
--cc=hch@infradead.org \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.