From: "Paul B. Henson" <henson@acm.org>
To: 'device-mapper development' <dm-devel@redhat.com>
Subject: Re: dm-writeboost: Progress Report
Date: Mon, 13 Jan 2014 13:03:11 -0800 [thread overview]
Message-ID: <061401cf10a2$e059ed90$a10dc8b0$@acm.org> (raw)
In-Reply-To: <52D3D21B.8030408@gmail.com>
> Akira Hayakawa
> Sent: Monday, January 13, 2014 3:47 AM
>
> This is because Writeboost makes a log on the RAM and writes it out to the
> cache device in sequential manner. I don't think other cache softwares can
> achieve this high level of throughput.
Would I be incorrect in assuming that this increased write performance comes
with the trade-off of a greater risk of losing data in the case of power
failure or crash?
next prev parent reply other threads:[~2014-01-13 21:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-11 7:27 dm-writeboost: Progress Report Akira Hayakawa
2014-01-13 10:09 ` Joe Thornber
2014-01-13 11:46 ` Akira Hayakawa
2014-01-13 15:14 ` Mike Snitzer
2014-01-13 21:03 ` Paul B. Henson [this message]
2014-01-19 1:16 ` Akira Hayakawa
2014-01-14 10:17 ` Joe Thornber
-- strict thread matches above, loose matches on Subject: below --
2014-05-17 14:44 Akira Hayakawa
2014-05-23 13:14 ` Akira Hayakawa
2013-11-04 5:17 Akira Hayakawa
2013-11-17 11:23 ` 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='061401cf10a2$e059ed90$a10dc8b0$@acm.org' \
--to=henson@acm.org \
--cc=dm-devel@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