public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lutz Vieweg <lkv@isg.de>
To: Michael Clark <michael@metaparadigm.com>
Cc: Robin Holt <holt@sgi.com>, linux-kernel@vger.kernel.org
Subject: Re: How to find out which pages were copied-on-write?
Date: Tue, 13 Jul 2004 15:04:04 +0200	[thread overview]
Message-ID: <40F3DDC4.7060104@isg.de> (raw)
In-Reply-To: <40F36216.1080603@metaparadigm.com>

Michael Clark wrote:

>> But wouldn't that introduce a significant overhead and undermine all 
>> of the
>> nice advantages the kernel might have in scheduling I/O operations?
>  
> Not really. Plain read/write IO is generally faster than mmap IO anyway.

Well, that was my result, too, when I measured mmap() vs. read()/write()
with the 2.4.x kernels, however, I was quite impressed recently when
I measured write operations with MAP_SHARED regions under 2.6.7
(CPU x86_64), they were not at all slower than ordinary write()s.
(congratulations to the involved kernel hackers on that! :-)

> You don't use mmap for speed but rather for convenience.

But isn't an advantage with mmap() that there's no need for the kernel
to copy what is to be written to a dedicated buffer? The kernel
could initiate DMA writes directly from the working memory...

Regards,

Lutz Vieweg



  reply	other threads:[~2004-07-13 13:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-06 15:58 How to find out which pages were copied-on-write? Lutz Vieweg
2004-07-09 11:31 ` Robin Holt
2004-07-09 20:42   ` Lutz Vieweg
2004-07-10  8:11     ` Michael Clark
2004-07-12 17:21       ` Lutz Vieweg
2004-07-13  4:16         ` Michael Clark
2004-07-13 13:04           ` Lutz Vieweg [this message]
2004-07-13 15:02             ` Michael Clark
2004-07-13 15:39               ` Lutz Vieweg
2004-07-14  0:25                 ` Michael Clark

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=40F3DDC4.7060104@isg.de \
    --to=lkv@isg.de \
    --cc=holt@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=michael@metaparadigm.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