All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bart Van Assche <bvanassche@acm.org>
To: Akira Hayakawa <ruby.wktk@gmail.com>
Cc: snitzer@redhat.com, gregkh@linuxfoundation.org,
	driverdev-devel@linuxdriverproject.org, thornber@redhat.com,
	linux-kernel@vger.kernel.org,
	device-mapper development <dm-devel@redhat.com>
Subject: Re: [dm-devel] [PATCH v2] staging: writeboost: Add dm-writeboost
Date: Fri, 12 Dec 2014 10:12:18 +0100	[thread overview]
Message-ID: <548AB172.4000103@acm.org> (raw)
In-Reply-To: <548A39E7.80508@gmail.com>

On 12/12/14 01:42, Akira Hayakawa wrote:
> 1. Writeboost shouldn't split the bio into 4KB chunks.
> No. It is necessary.
> I know WALB (https://github.com/starpos/walb) logs data without
> splitting but the data structure becomes complicated.
> If you read my code carefully, you will notice that splitting
> helps the design simplicity and performance.

This is the first time I see someone claiming that reducing the request 
size improves performance. I don't know any SSD model for which 
splitting requests improves performance.

Additionally, since bio's are split by dm-writeboost, this makes me 
wonder how atomic writes will ever be supported ? Atomic writes are 
being standardized by the T10 SCSI committee. I don't think the Linux 
block layer already supports atomic writes today but I expect support 
for atomic writes to be added to the block layer sooner or later. See 
e.g. http://www.t10.org/doc13.htm / SBC-4 SPC-5 Atomic writes and reads 
for the latest draft specification.

Bart.

  reply	other threads:[~2014-12-12  9:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10 11:42 [PATCH v2] staging: writeboost: Add dm-writeboost Akira Hayakawa
2014-12-11 15:26 ` Mike Snitzer
2014-12-12  0:42   ` Akira Hayakawa
2014-12-12  9:12     ` Bart Van Assche [this message]
2014-12-12  9:35       ` [dm-devel] " Akira Hayakawa
2014-12-12  9:35         ` Akira Hayakawa
2014-12-12 11:41         ` Bart Van Assche
2014-12-12 22:18           ` Spelic
2014-12-13  7:08             ` Jianjian Huo
2014-12-12 14:24     ` Joe Thornber
2014-12-12 14:24       ` Joe Thornber
2014-12-12 15:09       ` Akira Hayakawa
2014-12-12 15:09         ` Akira Hayakawa
2014-12-13  6:45         ` [dm-devel] " Jianjian Huo
2014-12-13  6:45           ` Jianjian Huo
2014-12-13 14:07           ` Akira Hayakawa
2014-12-13 14:07             ` Akira Hayakawa
2014-12-14  2:12             ` Akira Hayakawa
2014-12-14  2:12               ` Akira Hayakawa
2014-12-14  2:46             ` Jianjian Huo
2014-12-14  2:46               ` Jianjian Huo
2014-12-14  3:22               ` Akira Hayakawa
2014-12-14  3:22                 ` Akira Hayakawa
2014-12-14  3:00         ` Akira Hayakawa
2014-12-14  3:00           ` 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=548AB172.4000103@acm.org \
    --to=bvanassche@acm.org \
    --cc=dm-devel@redhat.com \
    --cc=driverdev-devel@linuxdriverproject.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ruby.wktk@gmail.com \
    --cc=snitzer@redhat.com \
    --cc=thornber@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.