public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions•net>
To: Ben Greear <greearb@candelatech•com>,
	Ard Biesheuvel <ard.biesheuvel@linaro•org>
Cc: Herbert Xu <herbert@gondor•apana.org.au>,
	Andy Lutomirski <luto@amacapital•net>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail•com>,
	"<netdev@vger•kernel.org>" <netdev@vger•kernel.org>,
	"David S. Miller" <davem@davemloft•net>,
	"<linux-wireless@vger•kernel.org>"
	<linux-wireless@vger•kernel.org>,
	"linux-kernel@vger•kernel.org" <linux-kernel@vger•kernel.org>,
	Jouni Malinen <j@w1•fi>
Subject: Re: [PATCH] crypto: ccm - avoid scatterlist for MAC encryption
Date: Wed, 19 Oct 2016 18:00:22 +0200	[thread overview]
Message-ID: <1476892822.10092.15.camel@sipsolutions.net> (raw)
In-Reply-To: <5807984D.4050307@candelatech.com>

On Wed, 2016-10-19 at 08:59 -0700, Ben Greear wrote:
> 
> Do you actually expect performance regressions?  I'll be complaining
> if so, but will test first :)

I think we can expect this to use a bit more CPU time, but unless
you're very tight on that you probably shouldn't expect any throughput
difference.

johannes

      reply	other threads:[~2016-10-19 16:00 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-15 17:16 [PATCH] crypto: ccm - avoid scatterlist for MAC encryption Ard Biesheuvel
2016-10-17  7:28 ` Johannes Berg
2016-10-17  7:37   ` Ard Biesheuvel
2016-10-17  7:47     ` Johannes Berg
2016-10-17  7:50       ` Ard Biesheuvel
2016-10-17  7:57         ` Johannes Berg
2016-10-17 17:08     ` Andy Lutomirski
2016-10-17 17:21       ` Ard Biesheuvel
     [not found]         ` <CAKv+Gu-25OvTSbyE06Ln8N+HsqNyV1T6oOudK2tyAAOmmXXqgA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-10-19  3:31           ` Herbert Xu
2016-10-19  7:43             ` Johannes Berg
2016-10-19 15:08               ` Ard Biesheuvel
2016-10-19 15:59                 ` Ben Greear
2016-10-19 16:00                   ` Johannes Berg [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=1476892822.10092.15.camel@sipsolutions.net \
    --to=johannes@sipsolutions$(echo .)net \
    --cc=ard.biesheuvel@linaro$(echo .)org \
    --cc=davem@davemloft$(echo .)net \
    --cc=greearb@candelatech$(echo .)com \
    --cc=herbert@gondor$(echo .)apana.org.au \
    --cc=j@w1$(echo .)fi \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-wireless@vger$(echo .)kernel.org \
    --cc=luto@amacapital$(echo .)net \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=sergey.senozhatsky.work@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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