mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hugh Dickins <hugh@veritas.com>
To: Gleb Natapov <glebn@voltaire.com>
Cc: "Michael S. Tsirkin" <mst@mellanox.co.il>,
	Roland Dreier <roland@topspin.com>,
	linux-kernel@vger.kernel.org, openib-general@openib.org
Subject: Re: [openib-general] Re: [PATCH repost] PROT_DONTCOPY: ifiniband uverbs fork support
Date: Thu, 11 Aug 2005 15:17:01 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0508111512080.11178@goblin.wat.veritas.com> (raw)
In-Reply-To: <20050811140729.GU16361@minantech.com>

On Thu, 11 Aug 2005, Gleb Natapov wrote:
> On Thu, Aug 11, 2005 at 03:04:29PM +0100, Hugh Dickins wrote:
> > On Thu, 11 Aug 2005, Gleb Natapov wrote:
> > > What about the idea that was floating around about new VM flag that will
> > > instruct kernel to copy pages belonging to the vma on fork instead of mark
> > > them as cow?
> > 
> > It's a pretty good idea, and thanks for reminding us of it.
> > 
> > It suffers from the general difficulty with fixes within get_user_pages,
> > that we need down_write(&mm->mmap_sem) to split_vma, and even just to
> > update vm_flags, whereas get_user_pages is entered with down_read.
> > 
> Why do it form get_user_pages? Lets use madvise/mprotect interface.
> Program can mrpotect(VM_COPYONFORK) address range before registering it.

Perhaps.  But then it's more complicated than the VM_DONTCOPY we came from.

It's a good solution to the semantic divergence introduced by VM_DONTCOPY,
but most people seemed unworried by that aspect.

My trouble is that I'm waiting for a magic right solution to appear,
and none has struct me that way so far.

Hugh

  reply	other threads:[~2005-08-11 14:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-19 16:55 [PATCH] " Michael S. Tsirkin
2005-07-25 17:19 ` [PATCH repost] PROT_DONTCOPY: ifiniband uverbs " Michael S. Tsirkin
2005-07-26 12:30   ` Hugh Dickins
2005-07-26 13:35     ` Michael S. Tsirkin
2005-08-09 18:13       ` Hugh Dickins
2005-08-10  8:30         ` Michael S. Tsirkin
2005-08-10  8:39         ` [openib-general] " Gleb Natapov
2005-08-10 13:22           ` Hugh Dickins
2005-08-10 13:26             ` Gleb Natapov
2005-08-10 15:27               ` Hugh Dickins
2005-08-11  8:02                 ` Gleb Natapov
2005-08-11 14:04                   ` Hugh Dickins
2005-08-11 14:07                     ` Gleb Natapov
2005-08-11 14:17                       ` Hugh Dickins [this message]
2005-08-11 14:11                     ` Michael S. Tsirkin
2005-08-15 16:37                   ` Bill Jordan
2005-08-16  7:52                     ` Gleb Natapov

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.61.0508111512080.11178@goblin.wat.veritas.com \
    --to=hugh@veritas.com \
    --cc=glebn@voltaire.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mst@mellanox.co.il \
    --cc=openib-general@openib.org \
    --cc=roland@topspin.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

all inboxes | Powered by JetHome®