mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: Baolin Wang <baolin.wang@linaro.org>,
	Mike Snitzer <snitzer@redhat.com>,
	Alasdair G Kergon <agk@redhat.com>,
	dm-devel@redhat.com, neilb@suse.com, linux-raid@vger.kernel.org,
	jack@suse.cz, Arnd Bergmann <arnd@arndb.de>,
	LKML <linux-kernel@vger.kernel.org>,
	keith.busch@intel.com, jmoyer@redhat.com, tj@kernel.org,
	bart.vanassche@sandisk.com, "Garg, Dinesh" <dineshg@quicinc.com>
Subject: Re: [PATCH 0/2] Introduce the request handling for dm-crypt
Date: Fri, 13 Nov 2015 11:51:44 +0000	[thread overview]
Message-ID: <20151113115144.GR12392@sirena.org.uk> (raw)
In-Reply-To: <5644AFA2.6040201@kernel.dk>

[-- Attachment #1: Type: text/plain, Size: 1126 bytes --]

On Thu, Nov 12, 2015 at 08:26:26AM -0700, Jens Axboe wrote:
> On 11/12/2015 03:04 AM, Mark Brown wrote:

> >Android now wants to encrypt phones and tablets by default and have been
> >seeing substantial performance hits as a result, we can try to get
> >people to share performance data from productionish systems but it might
> >be difficult.

> Well, shame on them for developing out-of-tree, looks like they are reaping
> all the benefits of that.

> Guys, we need some numbers, enough with the hand waving. There's no point
> discussing this further until we know how much of a difference it makes to
> handle X MB chunks instead of Y MB chunks. As was previously stated, unless
> there's a _substantial_ performance benefit, this patchset isn't going
> anywhere.

Yeah, what I'm saying here is that there will issues getting the numbers
from relevant production systems - we are most likely to be looking at
proxies which are hopefully reasonably representative but there's likely
to be more divergence than you'd see just running benchmark workloads on
similar systems to those used in production.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  parent reply	other threads:[~2015-11-13 11:52 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-11  9:31 Baolin Wang
2015-11-11  9:31 ` [PATCH 1/2] block: Introduce BIO_ENDIO_FREE for bio flags Baolin Wang
2015-11-11 17:54   ` Mike Snitzer
2015-11-12  4:05     ` Baolin Wang
2015-11-11  9:31 ` [PATCH 2/2] md: dm-crypt: Introduce the request handling for dm-crypt Baolin Wang
2015-11-11  9:48 ` [PATCH 0/2] " Christoph Hellwig
2015-11-12  2:15   ` Baolin Wang
2015-11-12  9:17     ` Jan Kara
2015-11-12  9:40       ` Baolin Wang
2015-11-12 11:06         ` Jan Kara
2015-11-12 11:46           ` Baolin Wang
2015-11-12 12:24             ` Jan Kara
2015-11-12 12:51               ` Baolin Wang
2015-11-12 12:57                 ` Arnd Bergmann
2015-11-12 15:02                   ` Mark Brown
2015-11-13  3:27                     ` Baolin Wang
2015-11-13  3:25                   ` Baolin Wang
2015-11-12 12:59                 ` Jan Kara
2015-11-13  2:05                   ` Baolin Wang
2015-11-13  9:05                     ` Arnd Bergmann
2015-11-13 11:37                       ` Baolin Wang
2015-11-11 18:18 ` Mike Snitzer
2015-11-12  2:36   ` Baolin Wang
2015-11-12  9:06     ` [dm-devel] " Christoph Hellwig
2015-11-12  8:20   ` Baolin Wang
2015-11-12 10:04     ` Mark Brown
2015-11-12 15:26       ` Jens Axboe
2015-11-13  2:07         ` Baolin Wang
2015-11-13 11:51         ` Mark Brown [this message]
2015-12-02 12:46           ` Baolin Wang
2015-12-02 19:56             ` [dm-devel] " Alasdair G Kergon
2015-12-03  2:56               ` Baolin Wang
2015-12-03 10:36                 ` Baolin Wang
2015-12-03 11:07                   ` Zdenek Kabelac
2015-12-03 11:27                     ` Baolin Wang
2015-12-03 15:49                   ` Mikulas Patocka
2015-12-04  4:58                     ` Baolin Wang
2015-12-03 15:47                 ` Mikulas Patocka
2015-12-04  4:57                   ` Baolin Wang
2015-11-12  9:05   ` Christoph Hellwig

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=20151113115144.GR12392@sirena.org.uk \
    --to=broonie@kernel.org \
    --cc=agk@redhat.com \
    --cc=arnd@arndb.de \
    --cc=axboe@kernel.dk \
    --cc=baolin.wang@linaro.org \
    --cc=bart.vanassche@sandisk.com \
    --cc=dineshg@quicinc.com \
    --cc=dm-devel@redhat.com \
    --cc=jack@suse.cz \
    --cc=jmoyer@redhat.com \
    --cc=keith.busch@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.com \
    --cc=snitzer@redhat.com \
    --cc=tj@kernel.org \
    /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

all inboxes | Powered by JetHome®