From: Joe Thornber <thornber@redhat.com>
To: Akira Hayakawa <ruby.wktk@gmail.com>
Cc: ejt@redhat.com, Greg KH <gregkh@linuxfoundation.org>,
snitzer@redhat.com, dm-devel@redhat.com,
driverdev-devel@linuxdriverproject.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] staging: writeboost: Add dm-writeboost
Date: Fri, 20 Feb 2015 15:50:36 +0000 [thread overview]
Message-ID: <20150220155036.GB4740@debian> (raw)
In-Reply-To: <54E75201.9030202@gmail.com>
On Sat, Feb 21, 2015 at 12:25:53AM +0900, Akira Hayakawa wrote:
> Yes.
How big are your log chunks? Presumably they're relatively small (eg,
256k). In which case you can optimise for the common case where you
have enough bios to hand to build your log chunk by just referencing
the bio payloads, rather than copying. It's only the last bit of io
in a burst that should be using this copying slow path.
- Joe
next prev parent reply other threads:[~2015-02-20 15:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-01 8:44 [PATCH v3] staging: writeboost: Add dm-writeboost Akira Hayakawa
2015-01-18 0:09 ` Greg KH
2015-02-20 8:44 ` Akira Hayakawa
2015-02-20 15:06 ` Joe Thornber
[not found] ` <54E75201.9030202@gmail.com>
2015-02-20 15:50 ` Joe Thornber [this message]
2015-02-20 16:06 ` Akira Hayakawa
2015-02-20 16:17 ` Joe Thornber
2015-02-21 1:36 ` Akira Hayakawa
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=20150220155036.GB4740@debian \
--to=thornber@redhat.com \
--cc=dm-devel@redhat.com \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=ejt@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ruby.wktk@gmail.com \
--cc=snitzer@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