mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Milan Broz <mbroz@redhat.com>
Cc: device-mapper development <dm-devel@redhat.com>,
	Andi Kleen <andi@firstfloor.org>,
	agk@redhat.com, linux-kernel@vger.kernel.org,
	eric.dumazet@gmail.com
Subject: Re: [dm-devel] [PATCH] DM-CRYPT: Scale to multiple CPUs v2
Date: Tue, 20 Jul 2010 09:26:22 +0200	[thread overview]
Message-ID: <20100720072621.GB30592@basil.fritz.box> (raw)
In-Reply-To: <4C4444C2.6040607@redhat.com>

On Mon, Jul 19, 2010 at 02:27:46PM +0200, Milan Broz wrote:
>  On 06/01/2010 09:52 AM, Andi Kleen wrote:
> > DM-CRYPT: Scale to multiple CPUs v2
> >
> > Updated version with the per CPU access improvements Eric suggested.
> Hi,
> 
> seems that this approach is probably the best one we can use now...
> (I would better see threads in crypto layer but that's taken of
> the programme for today, seems.)
> 
> I did some tests and it works for me, even tries some strange stacked
> mapping etc.
> Do you have some exact numbers for particular tests btw?

I had some, but can't find them right now, sorry.

The original motivation was one benchmark on encrypted fs 
which gave terrible results. But unfortunately I didn't get updated
numbers with the patch for that one.

The patch also seems to already have a small user base,
at least I got a few requests for it.

> 
> Anyway, I have just one comment - please can we make the per-cpu attribute
> for IV generic? IOW not add explicit ie (ESSIV) but void * iv_private
> - see attached patch.

Fine for me.

> 
> (I'll try discuss this with Alasdair to review for next merge
> window, I think you requested that already in some private mail...)

Yes. Thanks.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.

      reply	other threads:[~2010-07-20  7:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01  7:52 Andi Kleen
2010-07-19 12:27 ` [dm-devel] " Milan Broz
2010-07-20  7:26   ` Andi Kleen [this message]

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=20100720072621.GB30592@basil.fritz.box \
    --to=andi@firstfloor.org \
    --cc=agk@redhat.com \
    --cc=dm-devel@redhat.com \
    --cc=eric.dumazet@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mbroz@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

Powered by JetHome