linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: David Wragg <dpw@doc.ic.ac.uk>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Stephen Tweedie <sct@redhat.com>
Subject: Re: limit on number of kmapped pages
Date: Thu, 25 Jan 2001 18:16:21 +0000	[thread overview]
Message-ID: <20010125181621.W11607@redhat.com> (raw)
In-Reply-To: <y7rofwxeqin.fsf@sytry.doc.ic.ac.uk>; from dpw@doc.ic.ac.uk on Wed, Jan 24, 2001 at 12:35:12AM +0000

Hi,

On Wed, Jan 24, 2001 at 12:35:12AM +0000, David Wragg wrote:
> 
> > And why do the pages need to be kmapped? 
> 
> They only need to be kmapped while data is being copied into them.

But you only need to kmap one page at a time during the copy.  There
is absolutely no need to copy the whole chunk at once.

--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:[~2001-01-25 18:16 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
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     ` Stephen C. Tweedie [this message]
2001-01-25 23:53       ` limit on number of kmapped pages 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=20010125181621.W11607@redhat.com \
    --to=sct@redhat.com \
    --cc=dpw@doc.ic.ac.uk \
    --cc=ebiederm@xmission.com \
    --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