linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@digeo.com>
To: David Chow <davidchow@shaolinmicro.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: buffer head read/write
Date: Tue, 10 Dec 2002 12:13:01 -0800	[thread overview]
Message-ID: <3DF64ACD.DABB5317@digeo.com> (raw)
In-Reply-To: 3DF4C40D.2010201@shaolinmicro.com

David Chow 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.

grep wait_on_buffer fs/ext2/*.c - you'll see lots of examples.  eg:

        mark_buffer_dirty(bh);
        if (sb->s_flags & MS_SYNCHRONOUS) {
                ll_rw_block (WRITE, 1, &bh);
                wait_on_buffer (bh);
        }

      parent reply	other threads:[~2002-12-10 20:13 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
2002-12-11  0:19     ` Bryan Henderson
2002-12-11 14:31       ` David Chow
2002-12-10 20:13 ` Andrew Morton [this message]

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=3DF64ACD.DABB5317@digeo.com \
    --to=akpm@digeo.com \
    --cc=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 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).