From: Christoph Lameter <clameter@engr.sgi.com>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: Re: [RFC] [PATCH 2.6.20-mm2] Optionally inherit mlockall() semantics across fork()/exec()
Date: Thu, 22 Feb 2007 15:09:29 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.64.0702221507080.22567@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <1172178237.5341.38.camel@localhost>
On Thu, 22 Feb 2007, Lee Schermerhorn wrote:
> Add an int to mm_struct to remember inheritance of future locks.
Should that not go into the task_struct rather than into mm_struct?
If you run your gizmo on a thread then all other threads of the process
will also be pinned.
Or put it into the vma like VM_MLOCK and inherit it when vmas are copied.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2007-02-22 23:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-22 21:03 Lee Schermerhorn
2007-02-22 23:09 ` Christoph Lameter [this message]
2007-02-23 14:58 ` Lee Schermerhorn
2007-02-23 19:16 ` Christoph Lameter
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=Pine.LNX.4.64.0702221507080.22567@schroedinger.engr.sgi.com \
--to=clameter@engr.sgi.com \
--cc=Lee.Schermerhorn@hp.com \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox