mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tommy Reynolds <reynolds@redhat.com>
To: "Steffen Persvold" <sp@scali.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Short question about the mmap method
Date: Fri, 4 Jan 2002 14:59:49 -0600	[thread overview]
Message-ID: <20020104145949.682d51c4.reynolds@redhat.com> (raw)
In-Reply-To: <3C360FD5.91285F5D@scali.no>
In-Reply-To: <3C360FD5.91285F5D@scali.no>

[-- Attachment #1: Type: text/plain, Size: 1007 bytes --]

Uttered "Steffen Persvold" <sp@scali.no>, spoke thus:

> Hi lkml readers,
> 
> I have a question regarding drivers implementing the mmap and nopage methods.
> In some references I've read that pages in kernel allocated memory (either
> allocated with kmalloc, vmalloc or__get_free_pages) should be set to reserved
> (mem_map_reserve or set_bit(PG_reserved, page->flags) before they can be
> mmap'ed to guarantee that they can't be swapped out. Is this true ?

[kv]malloc memory is _never_ subject to paging and can be mmap'ed with a
vengeance without resorting to mucking about with marking pages or the like.

You're working too hard ;-)

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- + -- -- -- -- -- -- -- -- -- --
Tommy Reynolds                               | mailto: <reynolds@redhat.com>
Red Hat, Inc., Embedded Development Services | Phone:  +1.256.704.9286
307 Wynn Drive NW, Huntsville, AL 35805 USA  | FAX:    +1.256.837.3839
Senior Software Developer                    | Mobile: +1.919.641.2923

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2002-01-04 21:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-04 20:25 Steffen Persvold
2002-01-04 20:59 ` Tommy Reynolds [this message]
2002-01-05  1:07   ` Steffen Persvold
2002-01-05  2:56     ` Steffen Persvold
2002-01-05  3:59       ` Steffen Persvold
2002-01-05 14:17 ` Roman Zippel
2002-01-05 17:52 Douglas Gilbert

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=20020104145949.682d51c4.reynolds@redhat.com \
    --to=reynolds@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sp@scali.no \
    /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

Powered by JetHome