All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Snitzer <snitzer@redhat.com>
To: Milan Broz <mbroz@redhat.com>
Cc: dm-devel@redhat.com, Mikulas Patocka <mpatocka@redhat.com>
Subject: Re: an optimization for dm-bufio and dm-integrity
Date: Wed, 19 Jul 2017 14:56:06 -0400	[thread overview]
Message-ID: <20170719185606.GB20480@redhat.com> (raw)
In-Reply-To: <25f78733-a371-068f-9465-830e65027940@redhat.com>

On Wed, Jul 19 2017 at 12:22pm -0400,
Milan Broz <mbroz@redhat.com> wrote:

> On 07/19/2017 05:39 PM, Mike Snitzer wrote:
> > On Wed, Jul 19 2017 at 11:30P -0400,
> > Mikulas Patocka <mpatocka@redhat.com> wrote:
> > 
> >> Hi Mike
> >>
> >> Some times ago, I sent this patch as dm-bufio optimization (it doesn't 
> >> have to write full buffers, it only writes a part of the buffer that 
> >> changed). You delayed the patch until the next kernel.
> >>
> >> Will you submit the patch to the current kernel?
> > 
> > Sorry about that.  It obviously fell off my radar.
> > 
> > I'll review it and see if I can make the justification for it going into
> > 4.13-rc2.  But unfortunately the 4.13 merge window closed this past
> > Sunday when Linus released v4.13-rc1
> > 
> > I'll let you know though, thanks.
> 
> Just FYI: I am just running some tests with the stack space fix and
> this patch and the performance improvement for 4k sectors is really big
> (compared to 4.12).

If you could quantify the performance improvement that would be helpful.

Are you also using the plugging patch?

  parent reply	other threads:[~2017-07-19 18:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 15:30 [PATCH] an optimization for dm-bufio and dm-integrity Mikulas Patocka
2017-07-19 15:39 ` Mike Snitzer
2017-07-19 16:22   ` Milan Broz
2017-07-19 18:00     ` Mikulas Patocka
2017-07-19 18:56     ` Mike Snitzer [this message]
2017-07-20  6:12       ` Milan Broz

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=20170719185606.GB20480@redhat.com \
    --to=snitzer@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=mbroz@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.