linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Stephen C. Tweedie" <sct@redhat.com>
To: V Ganesh <ganesh@vxindia.veritas.com>
Cc: linux-kernel@vger.rutgers.edu, Stephen Tweedie <sct@redhat.com>,
	linux-mm@kvack.org
Subject: Re: Possible optimization in ext2_file_write()
Date: Fri, 19 Mar 1999 14:48:21 GMT	[thread overview]
Message-ID: <199903191448.OAA01416@dax.scot.redhat.com> (raw)
In-Reply-To: <199903181816.XAA12650@vxindia.vxindia.veritas.com>

Hi,

On Thu, 18 Mar 1999 23:46:57 +0530 (IST), V Ganesh
<ganesh@vxindia.veritas.com> said:

> 	it looks like whenever we write a partial block which 
> doesn't exist in the buffer cache, ext2_file_write() (and
> possibly the write functions of other filesystems) directly
> reads that block from the block device without checking if
> it is present in the page cache. 

Correct...

> Of course, typical UNIX programs/shell jobs don't indulge in
> this kind of behaviour. General workstation usage (X,
> kernel compiles etc.) for a day caused only 32 unnecessary
> reads. 

... and also correct.

> So unless there are any specific application categories which
> require this I guess it's not worth the trouble to patch.

I'd agree (strongly).  It ties in with your next question:

> Anyone working on a VM revamp or buffer/page cache unification ?

Yes.  We still need the buffer cache (or something very like it) for
filesystem metadata caching and for block IO.  However, 2.3 _will_ see
us using the page cache for data writeback (and we already have
prototype patches to support that sort of behaviour).  The linux-mm
list has been discussing it for some time.

--Stephen
--
To unsubscribe, send a message with 'unsubscribe linux-mm my@address'
in the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://humbolt.geo.uu.nl/Linux-MM/

       reply	other threads:[~1999-03-19 14:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199903181816.XAA12650@vxindia.vxindia.veritas.com>
1999-03-19 14:48 ` Stephen C. Tweedie [this message]
1999-03-20 15:33   ` Manfred Spraul

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=199903191448.OAA01416@dax.scot.redhat.com \
    --to=sct@redhat.com \
    --cc=ganesh@vxindia.veritas.com \
    --cc=linux-kernel@vger.rutgers.edu \
    --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