linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Timur Tabi <timur.tabi@ammasso.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	kernelnewbies@nl.linux.org
Subject: Re: get_user_pages() still broken in 2.6
Date: Wed, 29 Sep 2004 16:01:34 +0100	[thread overview]
Message-ID: <20040929160134.A13683@infradead.org> (raw)
In-Reply-To: <415ACB29.5000104@ammasso.com>; from timur.tabi@ammasso.com on Wed, Sep 29, 2004 at 09:48:09AM -0500

On Wed, Sep 29, 2004 at 09:48:09AM -0500, Timur Tabi wrote:
> Christoph Hellwig wrote:
> 
> > get_user_pages locks the page in memory.  It doesn't do anything about ptes.
> 
> I don't understand the difference.  I thought a locked page is one that 
> stays in memory (i.e. isn't swapped out) and whose physical address 
> never changes.  Is that wrong?

Yes.  But if you're walking ptes you're looking at virtual addresses
somehow.  Can you send me a pointer to your code please?  I suspect
it's doing something terribly stupid.

--
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:"aart@kvack.org"> aart@kvack.org </a>

  reply	other threads:[~2004-09-29 15:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-28 22:40 Timur Tabi
2004-09-28 23:03 ` Christoph Hellwig
2004-09-28 23:21   ` Dave Hansen
2004-09-29 14:46     ` Timur Tabi
2004-09-29 14:48   ` Timur Tabi
2004-09-29 15:01     ` Christoph Hellwig [this message]
2004-09-29  4:49 ` opening a file inside the kernel module Rakesh Jagota
2004-09-29  5:00   ` Jeff Garzik
2004-09-29  5:56     ` Rakesh Jagota
2004-09-29 15:52       ` Stuart MacDonald, linux-kernel-owner

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=20040929160134.A13683@infradead.org \
    --to=hch@infradead.org \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=timur.tabi@ammasso.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