From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Steffen Klassert <steffen.klassert@secunet.com>,
David Miller <davem@davemloft.net>
Cc: Herbert Xu <herbert@gondor.apana.org.au>, netdev@vger.kernel.org
Subject: Re: [PATCH 1/4] xfrm: use vmalloc_node() for percpu scratches
Date: Fri, 01 Nov 2013 17:02:51 +0400 [thread overview]
Message-ID: <5273A67B.9070901@cogentembedded.com> (raw)
In-Reply-To: <1383292257-4634-2-git-send-email-steffen.klassert@secunet.com>
Hello.
On 01-11-2013 11:50, Steffen Klassert wrote:
> From: Eric Dumazet <edumazet@google.com>
> scratches are per cpu, we can use vmalloc_node() for proper
> NUMA affinity.
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Acked-by: Herbert Xu <herbert@gondor.apana.org.au>
> Signed-off-by: Steffen Klassert <steffen.klassert@secunet.com>
> ---
> net/xfrm/xfrm_ipcomp.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
> diff --git a/net/xfrm/xfrm_ipcomp.c b/net/xfrm/xfrm_ipcomp.c
> index 2906d52..b943c7f 100644
> --- a/net/xfrm/xfrm_ipcomp.c
> +++ b/net/xfrm/xfrm_ipcomp.c
> @@ -220,8 +220,8 @@ static void ipcomp_free_scratches(void)
>
> static void * __percpu *ipcomp_alloc_scratches(void)
> {
> - int i;
> void * __percpu *scratches;
> + int i;
This collateral change is not described in the changelog.
WBR, Sergei
next prev parent reply other threads:[~2013-11-01 13:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-01 7:50 pull request (net-next): ipsec-next 2013-11-01 Steffen Klassert
2013-11-01 7:50 ` [PATCH 1/4] xfrm: use vmalloc_node() for percpu scratches Steffen Klassert
2013-11-01 13:02 ` Sergei Shtylyov [this message]
2013-11-02 5:21 ` David Miller
2013-11-01 7:50 ` [PATCH 2/4] xfrm: Don't queue retransmitted packets if the original is still on the host Steffen Klassert
2013-11-01 7:50 ` [PATCH 3/4] net: esp{4,6}: remove padlen from struct esp_data Steffen Klassert
2013-11-01 7:50 ` [PATCH 4/4] net: esp{4,6}: get rid of " Steffen Klassert
2013-11-02 6:14 ` pull request (net-next): ipsec-next 2013-11-01 David Miller
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=5273A67B.9070901@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=davem@davemloft.net \
--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.