Linux Device Mapper development
 help / color / mirror / Atom feed
From: Joe Thornber <thornber@redhat.com>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: dm-devel@redhat.com, "Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: test needed for a dm-bufio patch
Date: Tue, 9 Jul 2013 18:00:49 +0100	[thread overview]
Message-ID: <20130709170048.GA25314@debian> (raw)
In-Reply-To: <alpine.LRH.2.02.1307021747280.2229@file01.intranet.prod.int.rdu2.redhat.com>

On Tue, Jul 02, 2013 at 05:51:50PM -0400, Mikulas Patocka wrote:
> Hi Joe
>
> Could you please try this patch
> http://people.redhat.com/agk/patches/linux/editing/dm-bufio-submit-writes-outside-lock.patch
> and test if it generates some regressions for dm-thin?

Hi Mikulas,

I've run a couple of cache tests and don't see any regressions.
performance is similar.  I'll include it in my tree since it seems to
be a good thing.

- Joe

      reply	other threads:[~2013-07-09 17:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 21:51 test needed for a dm-bufio patch Mikulas Patocka
2013-07-09 17:00 ` Joe Thornber [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=20130709170048.GA25314@debian \
    --to=thornber@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox