public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-kernel@vger.kernel.org, Alasdair Kergon <agk@redhat.com>,
	dm-devel@redhat.com
Subject: Re: [PATCH 2/4] md: add flush_idx support for stacked devices
Date: Tue, 14 Oct 2014 08:25:21 -0400	[thread overview]
Message-ID: <20141014122520.GA7243@redhat.com> (raw)
In-Reply-To: <1413281035-6483-3-git-send-email-dmonakhov@openvz.org>

On Tue, Oct 14 2014 at  6:03am -0400,
Dmitry Monakhov <dmonakhov@openvz.org> wrote:

> For single device mapping it is safe to introduce get_flush_idx conception.
> This cover most common case linear mapping for a single dev.

You really should email the entire patchset rather than forcing the need
to hunt for the remainder of the patches that actually provide context
for this change.

  reply	other threads:[~2014-10-14 12:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-14 10:03 [PATCH 0/4] blkdev: flush optimization Dmitry Monakhov
2014-10-14 10:03 ` [PATCH 1/4] blkdev: add flush generation counter Dmitry Monakhov
2014-10-16 14:24   ` Ming Lei
2014-10-16 15:14     ` Dmitry Monakhov
2014-10-18  9:59       ` Ming Lei
2014-10-18 11:52         ` Dmitry Monakhov
2014-10-14 10:03 ` [PATCH 2/4] md: add flush_idx support for stacked devices Dmitry Monakhov
2014-10-14 12:25   ` Mike Snitzer [this message]
2014-10-14 10:03 ` [PATCH 3/4] ext4: cleanup data integrity sync fo nonjournal mode Dmitry Monakhov
2014-10-14 10:03 ` [PATCH 4/4] ext4: Add fdatasync scalability optimization Dmitry Monakhov
2014-10-14 10:57   ` Christoph Hellwig
2014-10-14 11:25     ` Dmitry Monakhov
2014-10-14 11:35       ` Christoph Hellwig

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=20141014122520.GA7243@redhat.com \
    --to=snitzer@redhat.com \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=dmonakhov@openvz.org \
    --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