From: Andrew Morton <akpm@osdl.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Make ll_rw_block() wait for buffer lock
Date: Mon, 11 Jul 2005 16:28:46 -0700 [thread overview]
Message-ID: <20050711162846.40304ab0.akpm@osdl.org> (raw)
In-Reply-To: <20050711155108.GR12428@atrey.karlin.mff.cuni.cz>
Jan Kara <jack@suse.cz> wrote:
>
> attached patch adds an operation SWRITE to ll_rw_block(). When this
> operation is specified ll_rw_block() waits for a buffer lock and doesn't
> just skip the locked buffer. Under some circumstances we need to make
> sure that current data are really being sent to disk and the old
> ll_rw_block()'s behaviour makes this impossible to achieve (as in some
> places we lock and unlock buffer without sending it to disk).
Fair enough - it's certainly saner this way.
Ordinarily it would be nicer to add a new function for this, say
ll_sync_write_bufs(struct buffer_head **bufs, int nr)
rather than adding new interpretations to ll_rw_block().
But ll_rw_block() is such a familiar old thing that I guess there's not
much advantage in adding some new thing for people to remember.
prev parent reply other threads:[~2005-07-11 23:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-11 15:51 Jan Kara
2005-07-11 23:28 ` 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=20050711162846.40304ab0.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jack@suse.cz \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®