linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Nick Piggin <u3293115@anu.edu.au>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: Chuck Lever <chucklever@gmail.com>,
	apkm@osdl.org, linux-mm@kvack.org, steved@redhat.com
Subject: Re: [PATCH] Make invalidate_inode_pages2() work again
Date: Tue, 26 Sep 2006 16:24:45 +1000	[thread overview]
Message-ID: <4518C7AD.3090507@anu.edu.au> (raw)
In-Reply-To: <451884C1.8080209@yahoo.com.au>

Nick Piggin wrote:

> So I really dislike get_user_pages for reasons such as this. IMO it would
> be cool if get_user_pages when the caller wants to write, would return 
> with
> the page dirty and a bit set to prevent writeout from cleaning it 
> until it
> has been finished with (via put_user_pages).
>
> Actually, _ideally_, maybe keeping the mapping around (ie. holding at
> least a read lock on mmap_sem) would do the trick. The presence of the
> mapping will be seen by the invalidate routines[*], and in general things
> might be simplified.


No, I guess that isn't going to work, because it'll mean one thread can
DoS the others WRT mmap and brk. I'll look into the per-page flag bit
idea.

--

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

  reply	other threads:[~2006-09-26  6:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-25 23:15 Chuck Lever
2006-09-25 23:59 ` Nick Piggin
2006-09-26  1:20   ` Trond Myklebust
2006-09-26  1:39     ` Nick Piggin
2006-09-26  6:24       ` Nick Piggin [this message]
2006-09-26  1:42     ` Andrew Morton
2006-09-26  1:54       ` Nick Piggin

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=4518C7AD.3090507@anu.edu.au \
    --to=u3293115@anu.edu.au \
    --cc=Trond.Myklebust@netapp.com \
    --cc=apkm@osdl.org \
    --cc=chucklever@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=steved@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