linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: lord@sgi.com
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
	David Woodhouse <dwmw2@infradead.org>,
	linux-mm@kvack.org, riel@conectiva.com.br
Subject: Re: kmap_kiobuf()
Date: Thu, 29 Jun 2000 10:34:01 +0100	[thread overview]
Message-ID: <20000629103401.B3473@redhat.com> (raw)
In-Reply-To: <200006282016.PAA19321@jen.americas.sgi.com>; from lord@sgi.com on Wed, Jun 28, 2000 at 03:16:42PM -0500

Hi,

On Wed, Jun 28, 2000 at 03:16:42PM -0500, lord@sgi.com wrote:

> So we are currently using memory managed as an address space to do the
> caching of metadata. Everything is built up out of single pages, and when we
> need something bigger we glue it together into a larger chunk of address
> space.

What do you mean by "address space"?  If you mean kernel VA, then
there's a clear risk of fragmenting the kernel's remappable area and
ending up unable to find contiguous regions at all if you're not
careful.

> p.s. Woudn't the remapping of pages be a way to let modules etc get larger
> arrays of memory after boot time - doing it a few times is not going to
> kill the system.

That's what vmalloc does.  If you mean actually moving physical pages
to clear space, it's really not so simple --- what happens if you
encounter mlock()ed pages?  The kernel also mixes user pages with
pinned kernel data structures which simply cannot be moved, so it's
not straightforward to support that sort of thing.

Cheers,
 Stephen
--
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.eu.org/Linux-MM/

  parent reply	other threads:[~2000-06-29  9:34 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-28 20:16 kmap_kiobuf() lord
2000-06-28 21:22 ` kmap_kiobuf() Benjamin C.R. LaHaise
2000-06-29  9:34 ` Stephen C. Tweedie [this message]
2000-06-29 13:45   ` kmap_kiobuf() Steve Lord
  -- strict thread matches above, loose matches on Subject: below --
2000-06-28 16:52 kmap_kiobuf() lord
2000-06-28 18:06 ` kmap_kiobuf() Stephen C. Tweedie
2000-06-28 19:06   ` kmap_kiobuf() Manfred Spraul
2000-06-28 21:05   ` kmap_kiobuf() Andi Kleen
2000-06-28 15:54 kmap_kiobuf() lord
2000-06-28 16:06 ` kmap_kiobuf() David Woodhouse
2000-06-28 16:24   ` kmap_kiobuf() Benjamin C.R. LaHaise
2000-06-28 18:07   ` kmap_kiobuf() Stephen C. Tweedie
2000-06-28 18:45     ` kmap_kiobuf() David Woodhouse
2000-06-29  9:09       ` kmap_kiobuf() Stephen C. Tweedie
2000-06-28 17:46 ` kmap_kiobuf() Stephen C. Tweedie
2000-06-28 15:41 kmap_kiobuf() David Woodhouse
2000-06-28 17:44 ` kmap_kiobuf() Stephen C. Tweedie
2000-06-29 10:52 ` kmap_kiobuf() Stephen C. Tweedie

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=20000629103401.B3473@redhat.com \
    --to=sct@redhat.com \
    --cc=dwmw2@infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=lord@sgi.com \
    --cc=riel@conectiva.com.br \
    /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