mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: <mheinz@infiniconsys.com>
To: unlisted-recipients:; (no To-header on input)@localhost.localdomain
Subject: Reference counts versus PG_locked and memory management....
Date: Wed, 15 Aug 2001 11:48:30 -0400	[thread overview]
Message-ID: <20010815154837Z271233-761+1477@vger.kernel.org> (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?

                 reply	other threads:[~2001-08-15 15:48 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=20010815154837Z271233-761+1477@vger.kernel.org \
    --to=mheinz@infiniconsys.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

all inboxes | Powered by JetHome®