linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: David Wragg <dpw@doc.ic.ac.uk>
Cc: "Benjamin C.R. LaHaise" <blah@kvack.org>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: limit on number of kmapped pages
Date: 24 Jan 2001 07:27:05 -0700	[thread overview]
Message-ID: <m1n1chdo06.fsf@frodo.biederman.org> (raw)
In-Reply-To: David Wragg's message of "24 Jan 2001 10:09:22 +0000"

David Wragg <dpw@doc.ic.ac.uk> writes:

> I'd still like to know what the basis for the current kmap limit
> setting is.

Mostly at one point kmap_atomic was all there was.  It was only the
difficulty of implementing copy_from_user with kmap_atomic that convinced
people we needed something more.  So actually if we can kmap several
megabyte at once the kmap limit is quite high.

Eric

--
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/

  reply	other threads:[~2001-01-24 14:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <y7rsnmav0cv.fsf@sytry.doc.ic.ac.uk>
2001-01-23 18:23 ` Eric W. Biederman
2001-01-24  0:35   ` David Wragg
2001-01-24  2:03     ` Benjamin C.R. LaHaise
2001-01-24 10:09       ` David Wragg
2001-01-24 14:27         ` Eric W. Biederman [this message]
2001-01-25 10:06         ` Random thoughts on sustained write performance Daniel Phillips
     [not found]           ` <y7rsnm7mai7.fsf@sytry.doc.ic.ac.uk>
     [not found]             ` <01012615062602.20169@gimli>
2001-01-27 13:50               ` David Wragg
2001-01-27 17:23                 ` Daniel Phillips
2001-01-27 21:23                   ` David Wragg
2001-01-25 18:16     ` limit on number of kmapped pages Stephen C. Tweedie
2001-01-25 23:53       ` David Wragg

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=m1n1chdo06.fsf@frodo.biederman.org \
    --to=ebiederm@xmission.com \
    --cc=blah@kvack.org \
    --cc=dpw@doc.ic.ac.uk \
    --cc=linux-kernel@vger.kernel.org \
    --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