From: Ric Wheeler <rwheeler@redhat.com>
To: Mike Snitzer <snitzer@gmail.com>
Cc: linux-raid@vger.kernel.org,
device-mapper development <dm-devel@redhat.com>,
Jens Axboe <jens.axboe@oracle.com>
Subject: Re: [PATCHES] new barriers - 2
Date: Fri, 17 Apr 2009 10:26:56 -0400 [thread overview]
Message-ID: <49E891B0.4080103@redhat.com> (raw)
In-Reply-To: <170fa0d20901300904l31d0c143ya02d6fb4de28c281@mail.gmail.com>
Mike Snitzer wrote:
> On Fri, Jan 30, 2009 at 5:15 AM, Tomasz Chmielewski <mangoo@wpkg.org> wrote:
>
>>> Here I announce 2nd version my new barrier support patches:
>>> http://people.redhat.com/mpatocka/patches/kernel/barriers/
>>>
>>> They are against 2.6.29-rc3.
>>>
>>> The most important enhancement is that with these patches, device mapper
>>> is able to send barrier requests to lower devices.
>>>
>> I guess it still won't work for those using LVM on md (Linux software RAID)
>> because md lacks barrier support? Do you know if someone is working on it?
>>
>
> md raid1 has supported barriers since 2.6.17
>
> But I'm not aware of any md work being done to support barriers in
> other raid levels. Judging by Neil Brown's thoughts on the matter
> (from 2006) it would seem unlikely he is putting effort to it, please
> see the following thread:
> http://marc.info/?l=linux-raid&m=115321319003578&w=2
> http://marc.info/?l=linux-raid&m=115335249503450&w=2
>
> cc'ing linux-raid to see if others have more insight
>
Neil, Hannes,
Is Mike's assumption above still true - no plans/thoughts about doing
barrier support for RAID5/6 and so on?
At least some things (the null barrier op) are in place now since your
summary of a couple years back, does this make it easier?
Thanks!
Ric
prev parent reply other threads:[~2009-04-17 14:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4982D33E.60000@wpkg.org>
2009-01-30 17:04 ` [dm-devel] [PATCHES] new barriers - 2 Mike Snitzer
2009-04-17 14:26 ` Ric Wheeler [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=49E891B0.4080103@redhat.com \
--to=rwheeler@redhat.com \
--cc=dm-devel@redhat.com \
--cc=jens.axboe@oracle.com \
--cc=linux-raid@vger.kernel.org \
--cc=snitzer@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;
as well as URLs for NNTP newsgroup(s).