From: Michael Heinz <mheinz@infiniconsys.com>
To: linux-kernel@vger.kernel.org
Subject: Implications of PG_locked and reference count in page structures....
Date: Wed, 15 Aug 2001 11:39:49 -0400 [thread overview]
Message-ID: <3B7A97C5.9090207@infiniconsys.com> (raw)
I'm in the process of porting a driver to Linux. The author of the
driver conveniently broke it into os-dependent and independent sections.
One of the things in the "OS" dependent section is a routine to lock a
section of memory presumably to be used for DMA.
So, what I want to do is this: given a pointer to a previously
kmalloc'ed block, and the length of that block, I want to (a) identify
each page associated with the block and (b) lock each page. It appears
that I can lock the page either by incrementing it's reference count, or
by setting the PG_locked flag for the page.
Which method is preferred? Is there another method I should be using
instead?
next reply other threads:[~2001-08-15 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-15 15:39 Michael Heinz [this message]
2001-08-15 16:04 ` Implications of PG_locked and reference count in page structures Ignacio Vazquez-Abrams
2001-08-15 17:04 ` Daniel Phillips
[not found] <no.id>
2001-08-15 15:55 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2001-08-15 17:10 Heinz, Michael
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=3B7A97C5.9090207@infiniconsys.com \
--to=mheinz@infiniconsys.com \
--cc=linux-kernel@vger.kernel.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