From: Jens Wilke <jens.wilke@de.ibm.com>
To: dm-devel@redhat.com
Cc: "Ming Zhao" <mingzhao99th@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: [dm-devel] [RFC][PATCH] dm-cache: block level disk cache target for device mapper
Date: Fri, 1 Dec 2006 11:30:04 +0100 [thread overview]
Message-ID: <200612011130.04466.jens.wilke@de.ibm.com> (raw)
In-Reply-To: <b1e142760611302316w5917bc67q5a9f26e1d069f716@mail.gmail.com>
On Friday 01 December 2006 08:16, Ming Zhao wrote:
> On 11/30/06, Jens Wilke <jens.wilke@de.ibm.com> wrote:
> > - You don't keep track of I/O on the fly to the cache that is mapped
> > directly in cache_hit(). How do you make sure that this I/O is completed
> > before you replace a cache block?
>
> The previous I/O from cache hit and the later I/O for cache
> replacement should be queued in order on the cache block device - is
> this a safe assumption?
I don't think you can assume that the request processing in the host
is ordered without sychronization. Everything you queue in your worker
thread is serialized by that. Everything else is out of your control and each
thread may be scheduled or not.
Maybe we have certain guarantees through DM or the block I/O layer, that
I don't know. Can somebody else step in here?
Best,
Jens
next prev parent reply other threads:[~2006-12-01 10:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-27 18:26 Eric Van Hensbergen
2006-11-27 18:47 ` bert hubert
2006-11-27 19:55 ` Eric Van Hensbergen
2006-12-02 1:21 ` [dm-devel] " Ming Zhang
2006-12-02 18:28 ` Ming Zhao
2006-12-02 18:35 ` Ming Zhang
2006-11-30 11:32 ` [dm-devel] " Jens Wilke
2006-11-30 16:24 ` Eric Van Hensbergen
2006-11-30 20:07 ` Jens Wilke
2006-12-01 7:16 ` Ming Zhao
2006-12-01 10:30 ` Jens Wilke [this message]
2006-11-30 14:48 ` Christoph Hellwig
2006-12-11 18:54 ` Eric Van Hensbergen
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=200612011130.04466.jens.wilke@de.ibm.com \
--to=jens.wilke@de.ibm.com \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingzhao99th@gmail.com \
/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®