linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Perez-Gonzalez, Inaky" <inaky.perez-gonzalez@intel.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linux-mm <linux-mm@kvack.org>
Subject: RE: Which is the proper way to bring in the backing store behindan inode as an struct page?
Date: Fri, 2 Jul 2004 12:42:26 -0700	[thread overview]
Message-ID: <F989B1573A3A644BAB3920FBECA4D25A6EBEE1@orsmsx407> (raw)

> From: Dave Hansen [mailto:haveblue@us.ibm.com]
> On Thu, 2004-07-01 at 23:34, Perez-Gonzalez, Inaky wrote:
> > Thus, what I need is a way that given the pair (inode,pgoff)
> > returns to me the 'struct page *' if the thing is cached in memory or
> > pulls it up from swap/file into memory and gets me a 'struct page *'.
> >
> > Is there a way to do this?
> 
> Do you have the VMA?  Why not just use the user mapping, and something
> like copy_to_user()?  It already handles all of the mess getting the
> page into memory and pulling it out of swap if necessary.
> 
> If you go into the page cache yourself, you'll have to deal with all of
> the usual !PageUptodate() and so forth.

No, I don't have the VMA :(; I can't really do copy_to_user() as
I just need to modify a word. I have gotten a suggestion to use
find_get_page() -- I am exploring that right now.

Thanks,

Inaky Perez-Gonzalez -- Not speaking for Intel -- all opinions are my own (and my fault)
--
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-07-02 19:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-02 19:42 Perez-Gonzalez, Inaky [this message]
2004-07-08  2:15 Perez-Gonzalez, Inaky
2004-07-08 23:56 ` Ram Pai

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=F989B1573A3A644BAB3920FBECA4D25A6EBEE1@orsmsx407 \
    --to=inaky.perez-gonzalez@intel.com \
    --cc=haveblue@us.ibm.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