From: Mike Snitzer <snitzer@redhat.com>
To: mpatocka@redhat.com
Cc: dm-devel@redhat.com, agk@redhat.com
Subject: Re: [patch 0/8] dm-bufio patches
Date: Mon, 26 Mar 2018 14:57:47 -0400 [thread overview]
Message-ID: <20180326185746.GA22409@redhat.com> (raw)
In-Reply-To: <20180326182939.169591126@debian.vm>
On Mon, Mar 26 2018 at 2:29pm -0400,
mpatocka@redhat.com <mpatocka@redhat.com> wrote:
> Hi
>
> Here I'm sending the second version of dm-bufio patches for arbitrary
> sector size.
>
> I dropped the patch that removes alloc_pages because it turns out that
> alloc_pages is faster than the slab allocator.
I had already staged the previous set, so I need to go back over that
and update accordingly.
> I also added a patch that removes struct bio from struct dm_buffer
> (reducing the size of dm_buffer to 1/3) and allocates the bio only when
> doing read or write.
OK, I'll go over your new set and try to tease out any differences.
Mike
next prev parent reply other threads:[~2018-03-26 18:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 18:29 [patch 0/8] dm-bufio patches mpatocka
2018-03-26 18:29 ` [patch 1/8] dm-bufio: move dm-bufio.h to include/linux/ mpatocka
2018-03-26 18:29 ` [patch 2/8] dm-bufio: get rid of slab cache name allocations mpatocka
2018-03-26 18:29 ` [patch 3/8] dm-bufio: remove code that merges slab caches mpatocka
2018-03-26 18:29 ` [patch 4/8] dm-bufio: fix slab cache attributes mpatocka
2018-03-26 18:29 ` [patch 5/8] dm-bufio recorder fields in dm-buffer mpatocka
2018-03-26 18:29 ` [patch 6/8] dm-bufio: use slab cache for dm_buffer mpatocka
2018-03-26 18:29 ` [patch 7/8] dm-bufio: support non-power-of-two block sizes mpatocka
2018-03-26 18:29 ` [patch 8/8] dm-bufio: dont embed bio in dm_buffer mpatocka
2018-03-26 18:57 ` Mike Snitzer [this message]
2018-03-26 20:20 ` [patch 0/8] dm-bufio patches Mikulas Patocka
2018-03-27 0:55 ` Mike Snitzer
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=20180326185746.GA22409@redhat.com \
--to=snitzer@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