Linux Device Mapper development
 help / color / mirror / Atom feed
From: Nikola Ciprich <extmaillist@linuxbox.cz>
To: Milan Broz <mbroz@redhat.com>
Cc: nikola.ciprich@linuxbox.cz,
	device-mapper development <dm-devel@redhat.com>,
	Alasdair G Kergon <agk@redhat.com>
Subject: Re: [RFC PATCH 0/4] dm core: full barrier support
Date: Thu, 7 Aug 2008 06:38:30 +0200	[thread overview]
Message-ID: <20080807043830.GA14595@nik-comp.linuxbox.cz> (raw)
In-Reply-To: <48997E09.9040808@redhat.com>

Hi,
and thanks for reply. OK, so I guess it might help if somebody (me:)) starts at least testing and commenting, right?
I'll install it on some of testing machines and report results.
br
nik

> No, there was no feedback.
> 
> Pushing it mainline depends on Alasdair's decision (maintainer of device-mapper).
> (It needs thorough review first and maybe better implementation.)
> 
> Milan
> --
> mbroz@redhat.com
> 
> 
> > thanks a lot in advance
> > BR
> > nik
> > 
> > On Tue, Jul 08, 2008 at 06:48:53PM +0200, Milan Broz wrote:
> >> Hi,
> >>
> >> there was several discussions about supporting barriers
> >> in device-mapper.
> >>
> >> I wrote this code some time ago, but it never reached dm-devel
> >> tree. Take this more like RFC and experimental approach
> >> - maybe there is better way how to handle it. 
> >> Anyway this implementation works in my tests and is relatively simple.
> >>
> >> [RFC PATCH 1/4] dm core: remove unused code
> >> 	- just remove never used code, already sent some time ago
> >> 	in another patchset
> >>
> >> [RFC PATCH 2/4] dm core: add support for empty barriers
> >> 	- the core implementation of empty barrier support
> >> 	- implementation for stripe target
> >>
> >> [RFC PATCH 3/4] dm core: add support for barrier bio with payload
> >> 	- tranform payload to sequence of data bio + empty barrier
> >>
> >> [RFC PATCH 4/4] dm core: wait for barrier in process in suspend
> >> 	- try to solve the problem that we cannot suspend device
> >> 	during processing of barrier.
> 

-- 
-------------------------------------
Nikola CIPRICH
LinuxBox.cz, s.r.o.
28. rijna 168, 709 01 Ostrava

tel.:   +420 596 603 142
fax:    +420 596 621 273
mobil:  +420 777 093 799

www.linuxbox.cz

mobil servis: +420 737 238 656
email servis: servis@linuxbox.cz
-------------------------------------

      reply	other threads:[~2008-08-07  4:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-08 16:48 [RFC PATCH 0/4] dm core: full barrier support Milan Broz
2008-08-06 10:05 ` Nikola Ciprich
2008-08-06 10:33   ` Milan Broz
2008-08-07  4:38     ` Nikola Ciprich [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=20080807043830.GA14595@nik-comp.linuxbox.cz \
    --to=extmaillist@linuxbox.cz \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=mbroz@redhat.com \
    --cc=nikola.ciprich@linuxbox.cz \
    /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