public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Clark <michael@metaparadigm.com>
To: Lutz Vieweg <lkv@isg.de>
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 12:16:22 +0800	[thread overview]
Message-ID: <40F36216.1080603@metaparadigm.com> (raw)
In-Reply-To: <40F2C882.7070406@isg.de>

On 07/13/04 01:21, Lutz Vieweg wrote:
> Michael Clark wrote:
> 
>> HPAs library LPSM sounds like what you're looking for.
>>
>> http://freshmeat.net/projects/lpsm/
>>
>> Or you can do what you want the hard way using mprotect and a SEGV 
>> handler.
> 
> 
> Certainly a valid idea to consider - doing all those things in 
> userspace... so
> thanks for the hint!
> 
> 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.
You don't use mmap for speed but rather for convenience.

> However, I shall really consider and profile the mprotect/sighandler 
> approach...
> 
> Regards,
> 
> Lutz Vieweg
> 
> PS: I'm using my own allocator already, so using the C-library 
> implementation
>     wouldn't gain me much...

This wasn't why I suggested it. It's has the commit semantics
on memory mapped files that you were asking about (the allocator
is optional I believe).

~mc

  reply	other threads:[~2004-07-13  4:16 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 [this message]
2004-07-13 13:04           ` Lutz Vieweg
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=40F36216.1080603@metaparadigm.com \
    --to=michael@metaparadigm.com \
    --cc=holt@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkv@isg.de \
    /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