linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: "Eric W. Biederman" <ebiederm+eric@npwt.net>
Cc: "Stephen C. Tweedie" <sct@redhat.com>,
	Hans Reiser <reiser@ricochet.net>,
	Shawn Leas <sleas@ixion.honeywell.com>,
	Reiserfs <reiserfs@devlinux.com>,
	Ken Tetrick <ktetrick@ixion.honeywell.com>,
	linux-mm@kvack.org
Subject: Re: (reiserfs) Re: More on Re: (reiserfs) Reiserfs and ext2fs (was Re: (reiserfs) Sum Benchmarks (these look typical?))
Date: Wed, 1 Jul 1998 21:07:32 +0100	[thread overview]
Message-ID: <199807012007.VAA04529@dax.dcs.ed.ac.uk> (raw)
In-Reply-To: <m13ecl7m25.fsf@flinx.npwt.net>

Hi,

On 01 Jul 1998 08:11:46 -0500, ebiederm+eric@npwt.net (Eric
W. Biederman) said:

ST> Read the source code!  We already do this.  If one process or thread
ST> msync()s a mapped file, its dirty pages get written to disk,
ST> independently of any other processes on the same or other CPUs which
ST> may still have the pages mapped and may still be writing to them.  We
ST> don't unmap pages for write; we just mark them non-dirty around all
ST> ptes.

> I just took the time and looked.  

> And in buffer.c in get_hash_table if we are returning a locked buffer,
> we always wait on that buffer until it is unlocked.  So to date we I
> don't see us tempting fate, with writing to locked buffers.

Whoops, yes, we do currently do copies for msync().  It's been too long
since I was digging in that code...

--Stephen

  reply	other threads:[~1998-07-01 22:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.HPP.3.96.980617035608.29950A-100000@ixion.honeywell.com>
     [not found] ` <199806221138.MAA00852@dax.dcs.ed.ac.uk>
     [not found]   ` <358F4FBE.821B333C@ricochet.net>
     [not found]     ` <m11zsgrvnf.fsf@flinx.npwt.net>
     [not found]       ` <199806241154.MAA03544@dax.dcs.ed.ac.uk>
     [not found]         ` <m11zse6ecw.fsf@flinx.npwt.net>
1998-06-25 11:00           ` Stephen C. Tweedie
1998-06-26 15:56             ` Eric W. Biederman
1998-06-29 10:35               ` Stephen C. Tweedie
1998-06-29 19:59                 ` Eric W. Biederman
1998-06-30 16:10                   ` Stephen C. Tweedie
1998-07-01  0:17                     ` Eric W. Biederman
1998-07-01  9:12                       ` Stephen C. Tweedie
1998-07-01 12:45                         ` Eric W. Biederman
1998-07-01 13:11                         ` Eric W. Biederman
1998-07-01 20:07                           ` Stephen C. Tweedie [this message]
1998-07-02 15:17                             ` Eric W. Biederman

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=199807012007.VAA04529@dax.dcs.ed.ac.uk \
    --to=sct@redhat.com \
    --cc=ebiederm+eric@npwt.net \
    --cc=ktetrick@ixion.honeywell.com \
    --cc=linux-mm@kvack.org \
    --cc=reiser@ricochet.net \
    --cc=reiserfs@devlinux.com \
    --cc=sleas@ixion.honeywell.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