linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Lee Schermerhorn <Lee.Schermerhorn@hp.com>
Cc: linux-mm@kvack.org, riel@redhat.com, hugh@veritas.com,
	kosaki.motohiro@jp.fujitsu.com, a.p.zijlstra@chello.nl
Subject: Re: [PATCH/RFC] - support inheritance of mlocks across fork/exec
Date: Tue, 25 Nov 2008 15:26:51 -0800	[thread overview]
Message-ID: <20081125152651.b4c3c18f.akpm@linux-foundation.org> (raw)
In-Reply-To: <1227561707.6937.61.camel@lts-notebook>

On Mon, 24 Nov 2008 16:21:46 -0500
Lee Schermerhorn <Lee.Schermerhorn@hp.com> wrote:

> PATCH/RFC - support inheritance of mlocks across fork/exec

Linux actually used to do this by mistake.  We fixed it in
2.3.<mumble>, iirc.

> Against;  2.6.28-rc5-mmotm-081121
> 
> Add support for mlockall(MCL_INHERIT|MCL_RECURSIVE):
> 	MCL_CURRENT|MCL_INHERIT - inherit memory locks across fork()
> 	MCL_FUTURE|MCL_INHERIT - inherit "MCL_FUTURE" semantics across
> 	fork() and exec().
> 	MCL_RECURSIVE - inherit across future generations.
> 
> In support of a "lock prefix command"--e.g., mlock <cmd> <args> ...

I spent some time scratching my head over what "MCL_RECURSIVE - inherit
across future generations" means, then decided that I shouldn't need to
scratch.

This patch should get wider attention than just linux-mm denizens,
methinks.

So can you please beef up the MCL_RECURSIVE description, then resend
the patch, also cc'ing linux-kernel@vger.kernel.org,
linux-api@vger.kernel.org and linux-arch@vger.kernel.org?

Thanks.

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

  parent reply	other threads:[~2008-11-25 23:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-24 21:21 Lee Schermerhorn
2008-11-25  4:05 ` KOSAKI Motohiro
2008-11-25 16:21 ` Rik van Riel
2008-11-25 23:26 ` Andrew Morton [this message]
2008-12-03 19:04   ` [PATCH] - support inheritance of mlocks across fork/exec V2 Lee Schermerhorn
2008-12-04  1:57     ` KOSAKI Motohiro
2008-12-07  6:07     ` Andrew Morton
2008-12-08 15:01       ` Lee Schermerhorn
2008-12-08 21:05       ` Lee Schermerhorn
2008-12-08 21:33         ` Matt Mackall
2008-12-09 19:40           ` Lee Schermerhorn
2008-12-09 20:41             ` Matt Mackall
2009-06-05  4:39     ` Jon Masters
2009-06-05  4:49       ` KOSAKI Motohiro
2009-06-05  5:12         ` Jon Masters
2008-11-26  8:37 ` [PATCH/RFC] - support inheritance of mlocks across fork/exec KOSAKI Motohiro
2008-11-29 22:38   ` Lee Schermerhorn
2008-11-30  5:21     ` KOSAKI Motohiro

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=20081125152651.b4c3c18f.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=Lee.Schermerhorn@hp.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=hugh@veritas.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-mm@kvack.org \
    --cc=riel@redhat.com \
    /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