From: David Chow <davidchow@shaolinmicro.com>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: buffer head read/write
Date: Tue, 10 Dec 2002 22:56:03 +0800 [thread overview]
Message-ID: <3DF60083.2010101@shaolinmicro.com> (raw)
In-Reply-To: 15861.14090.224979.12485@notabene.cse.unsw.edu.au
Neil Brown wrote:
>On Tuesday December 10, davidchow@shaolinmicro.com wrote:
>
>
>>Hi all,
>>
>>Is there a way to make sure I submit a buffer head read/write and make
>>sure it is commited immediately? (sychronized) . Please give direction
>>on examples in the kernel code? Thanks.
>>
>>
>
>md does (or will) read/write it's super-blocks that way.
>In 2.5, see drivers/md/md.c:sync_page_io
>In 2.4, see
> http://cgi.cse.unsw.edu.au/~neilb/patches/linux-stable/2.4.leading/2002-12-09:01/005MDSyncIo
>
>... I haven't submitted it yet.
>
>NeilBrown
>
>
Thanks to all who give suggestions. I know how to make a call to
general_make_request() but wait for the buffer to complete which is too
slow. If I am doing a continuous sychronous read/write (which I already
have my own way of buffer management), can I put those "dirty
buffers"/"non-up-to-date buffers" in the head of the buffer queue so
that they get written by their respective handler immediately? I am not
familiar with buffer cache so would like to seek advice on doing this.
Is there anyway to lock a buffer and get its buffer_head request handler
and call end_io() immediately? Thanks for advice.
regards,
David Chow
next prev parent reply other threads:[~2002-12-10 14:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 16:25 buffer head read/write David Chow
2002-12-10 0:28 ` Bryan Henderson
2002-12-10 0:36 ` Neil Brown
2002-12-10 14:56 ` David Chow [this message]
2002-12-11 0:19 ` Bryan Henderson
2002-12-11 14:31 ` David Chow
2002-12-10 20:13 ` Andrew Morton
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=3DF60083.2010101@shaolinmicro.com \
--to=davidchow@shaolinmicro.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=neilb@cse.unsw.edu.au \
/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;
as well as URLs for NNTP newsgroup(s).