All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Chow <davidchow@shaolinmicro.com>
To: linux-fsdevel@vger.kernel.org
Subject: write back caching, async writes
Date: Sun, 21 Apr 2002 01:56:39 +0800	[thread overview]
Message-ID: <3CC1ABD7.3040800@shaolinmicro.com> (raw)

If I want to implement a write back cache or async write in an fs, how 
can I make vfs call back to write by cache or any way to schedule some 
tasks so that the kernel will commit the current task but have a call 
back later? For filesystem methods, it seems it is a process context 
stuff, the only way I can think is to use mark_inode_dirty() so that vfs 
will call my write_inode() super_block_ops so that it works like 
schedule something to write later. If so, how can I retain the page 
cache that has already called to my commit_write() so that those clean 
pages (actually not in disk for async case) can be retained and I can 
make use of those pages when I actuallly sync the data to disk. Or 
should I have a private researved area of buffer to take care of those 
async pages? Please give suggestions. Thanks.

David


                 reply	other threads:[~2002-04-20 17:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3CC1ABD7.3040800@shaolinmicro.com \
    --to=davidchow@shaolinmicro.com \
    --cc=linux-fsdevel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.