From: Anthony Nicholson <nicholson_anthony@yahoo.com>
To: linux-mm@kvack.org
Subject: matching pages with their owner process(es)
Date: Mon, 23 Jun 2003 02:12:14 -0700 (PDT) [thread overview]
Message-ID: <20030623091214.5259.qmail@web13608.mail.yahoo.com> (raw)
anyone know how to determine, from a struct page *, which
process is the owner of the data in that frame? it doesn't
seem from what i've seen in the source, and from what i've
read that there's any easy way to do it.
i'm working on swap space encryption, but need to not
encrypt/decrypt the swap for a few special processes that
i'm ignoring.
basically i want to be able to tell in rw_swap_page()
from the page* which processes' memory this is. any idea?
thanks
anthony
__________________________________
Do you Yahoo!?
SBC Yahoo! DSL - Now only $29.95 per month!
http://sbc.yahoo.com
--
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:[~2003-06-23 9:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030623091214.5259.qmail@web13608.mail.yahoo.com \
--to=nicholson_anthony@yahoo.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