From: Milan Broz <mbroz@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
Alasdair G Kergon <agk@redhat.com>
Subject: Re: [PATCH 0/4][RFC] dm-core: full barrier support
Date: Mon, 12 Jan 2009 14:01:16 +0100 [thread overview]
Message-ID: <496B3F1C.6050709@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0901111319240.25677@hs20-bc2-1.build.redhat.com>
Mikulas Patocka wrote:
> I looked at the patches.
Thanks - the patchset was meant more like impulse to start discussion:-)
This implementation uses just simple idea to reuse dm suspend mechanism
for barrier processing.
> I have thought about it and written an implementation of asynchronous
> barriers --- it works by passing the requests to kdmflush and it returns
> immediatelly from dm_request. I'll post it in a few days.
Great. I'll wait for the patches then:)
The internal thread was added to DM devices mainly because of implementing
barriers but this intention was never finished...
Milan
--
mbroz@redhat.com
prev parent reply other threads:[~2009-01-12 13:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-08 16:13 [PATCH 0/4][RFC] dm-core: full barrier support Milan Broz
2009-01-11 19:28 ` Mikulas Patocka
2009-01-12 13:01 ` Milan Broz [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=496B3F1C.6050709@redhat.com \
--to=mbroz@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mpatocka@redhat.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 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.