All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathias Krause <mathias.krause@secunet.com>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: "David S. Miller" <davem@davemloft.net>,
	Steffen Klassert <steffen.klassert@secunet.com>,
	Dmitry Tarnyagin <dmitry.tarnyagin@lockless.no>,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next 3/3] net: allow to leave the buffer fragmented in skb_cow_data()
Date: Thu, 07 Nov 2013 11:01:10 +0100	[thread overview]
Message-ID: <527B64E6.9040004@secunet.com> (raw)
In-Reply-To: <20131107090135.GA385@gondor.apana.org.au>

On 07.11.2013 10:01, Herbert Xu wrote:
> On Thu, Nov 07, 2013 at 09:55:34AM +0100, Mathias Krause wrote:
>> Indeed. I want to avoid the costly memcpy() on the CPU serving the NIC
>> interrupt, as that is a bottleneck in my setup. The packet processing --
>> encrypting/decrypting of ESP packets -- gets mostly parallelized via
>> pcrypt, so that's fine. But the initial network processing, i.e. getting
>> to pcrypt, is what's throttling the throughput currently. (RPS only
>> partly solves this problem as for the ESP receive path most traffic ends
>> up on the same flow).
> 
> How about this: instead of doing in-place encryption/decryption
> let's allocate a new destination buffer and encrypt/decrypt into
> it.  Then we essentially get the copy for free.
> 
> So instead of modifying skb_cow_data you can change esp4.c, etc.

That might be another option. But I fear it might affect performance due
to caching or NUMA effects. :/

I'll think about it and will try to investigate both approaches.


Thanks,
Mathias

  reply	other threads:[~2013-11-07 10:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05 13:54 [PATCH net-next 0/3] IPsec improvements Mathias Krause
2013-11-05 13:54 ` [PATCH net-next 1/3] net: move pskb_put() to core code Mathias Krause
2013-11-05 18:33   ` Ben Hutchings
2013-11-06  9:01     ` Mathias Krause
2013-11-05 13:54 ` [PATCH net-next 2/3] caif: use pskb_put() instead of reimplementing its functionality Mathias Krause
2013-11-05 13:54 ` [PATCH net-next 3/3] net: allow to leave the buffer fragmented in skb_cow_data() Mathias Krause
2013-11-05 14:33   ` Eric Dumazet
2013-11-05 14:43     ` Mathias Krause
2013-11-06  9:30   ` Herbert Xu
2013-11-06  9:49     ` Mathias Krause
2013-11-06  9:52       ` Herbert Xu
2013-11-06 12:42         ` Mathias Krause
2013-11-06 12:48           ` Herbert Xu
2013-11-06 16:39             ` Eric Dumazet
2013-11-07  8:56               ` Mathias Krause
2013-11-07  8:55             ` Mathias Krause
2013-11-07  9:01               ` Herbert Xu
2013-11-07 10:01                 ` Mathias Krause [this message]
2013-11-06  4:48 ` [PATCH net-next 0/3] IPsec improvements David Miller
2013-11-06  9:02   ` Mathias Krause

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=527B64E6.9040004@secunet.com \
    --to=mathias.krause@secunet.com \
    --cc=davem@davemloft.net \
    --cc=dmitry.tarnyagin@lockless.no \
    --cc=herbert@gondor.apana.org.au \
    --cc=netdev@vger.kernel.org \
    --cc=steffen.klassert@secunet.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.