[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1288184405.2709.108.camel@edumazet-laptop>
Date: Wed, 27 Oct 2010 15:00:05 +0200
From: Eric Dumazet <eric.dumazet@...il.com>
To: Dmitry Popov <dp@...hloadlab.com>
Cc: "David S. Miller" <davem@...emloft.net>,
William.Allen.Simpson@...il.com,
Andreas Petlund <apetlund@...ula.no>,
Ilpo Järvinen <ilpo.jarvinen@...sinki.fi>,
Alexey Kuznetsov <kuznet@....inr.ac.ru>,
"Pekka Savola (ipv6)" <pekkas@...core.fi>,
James Morris <jmorris@...ei.org>,
Hideaki YOSHIFUJI <yoshfuji@...ux-ipv6.org>,
Patrick McHardy <kaber@...sh.net>,
Stephen Hemminger <shemminger@...tta.com>,
Herbert Xu <herbert@...dor.apana.org.au>,
Gilad Ben-Yossef <gilad@...efidence.com>,
Yony Amit <yony@...sleep.com>, Zhu Yi <yi.zhu@...el.com>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH] tcp: md5 signature check scaling
Le mercredi 27 octobre 2010 à 16:52 +0400, Dmitry Popov a écrit :
> From: Dmitry Popov <dp@...hloadlab.com>
>
> TCP MD5 signature checking without socket lock.
>
> Each tcp_sock has 2 RCU-protected arrays (tcp[46]_md5sig_info) of
> tcp[46]_md5sig_key address-key pairs.
> Each key (tcp_md5sig_key) has kref struct so that there is no need to
> lock the whole array to work with one key.
>
> MD5 functions were rewritten according to above statement and hash
> check (tcp_v4_inbound_md5_hash) was moved before socket lock.
>
> Signed-off-by: Dmitry Popov <dp@...hloadlab.com>
> ---
> include/linux/tcp.h | 14 ++-
> include/net/tcp.h | 82 +++++++----
> net/ipv4/tcp_ipv4.c | 370 ++++++++++++++++++++++++++++------------------
> net/ipv4/tcp_minisocks.c | 26 +--
> net/ipv4/tcp_output.c | 12 +-
> net/ipv6/tcp_ipv6.c | 358 +++++++++++++++++++++++++++-----------------
> 6 files changed, 531 insertions(+), 331 deletions(-)
This is a huge patch :(
Reading changelog, I dont understand what you did, and why you did this.
You want to avoid taking the socket lock ? But we need to take it anyway
to process packets.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists