linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: Rajagopal Ananthanarayanan <ananth@sgi.com>
Cc: linux-mm@kvack.org
Subject: Re: writeback list
Date: Thu, 13 Jul 2000 19:21:39 -0300 (BRST)	[thread overview]
Message-ID: <Pine.LNX.4.21.0007131917280.1215-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <396E2CC0.9B8BE5C7@sgi.com>

On Thu, 13 Jul 2000, Rajagopal Ananthanarayanan wrote:
> Rik van Riel wrote:

> > we may have forgotten something in our new new vm design from
> > last weekend. While we have the list head available to put
> > pages in the writeback list, we don't have an entry in to put
> > the timestamp of the write in struct_page...
> > 
> > Maybe we want to have an active list after all and replace the
> > buffer_head pointer with a pointer to another structure that
> > tracks the writeback stuff that's now tracked by the buffer head?
> > 
> > (things like: prev, next, write_time and a few other things)
> 
> Yes, maintaining time information in the page will be useful for
> XFS also. Basically, there are pages in the page cache without a
> particular block(s) assigned to the page ... these are the
> delayed allocate pages. Such pages don't have any buffer_heads
> associated with them, until the delalloc is converted.

Exactly, this is what the write-back list will be used for.

> It will be great if the delalloc pages can be somehow temporally
> ordered. The write-back list you propose seems to fit the bill
> nicely.

To put it more strongly, the write-back list *needs* to be
temporally ordered if we want to have a kupdate like we have
today.

regards,

Rik
--
"What you're running that piece of shit Gnome?!?!"
       -- Miguel de Icaza, UKUUG 2000

http://www.conectiva.com/		http://www.surriel.com/

--
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/

  reply	other threads:[~2000-07-13 22:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8kl5ij$4vtnc$1@fido.engr.sgi.com>
2000-07-13 20:55 ` Rajagopal Ananthanarayanan
2000-07-13 22:21   ` Rik van Riel [this message]
2000-07-13 19:30 Rik van Riel
2000-07-14  9:35 ` Stephen C. Tweedie
2000-07-14 13:35   ` Rik van Riel

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=Pine.LNX.4.21.0007131917280.1215-100000@duckman.distro.conectiva \
    --to=riel@conectiva.com.br \
    --cc=ananth@sgi.com \
    --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