From: Hannes Frederic Sowa <hannes@redhat.com>
To: "cristian.bercaru@freescale.com" <cristian.bercaru@freescale.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"R89243@freescale.com" <R89243@freescale.com>,
Madalin-Cristian Bucur <madalin.bucur@freescale.com>,
"Razvan.Ungureanu@freescale.com" <Razvan.Ungureanu@freescale.com>
Subject: Re: atomic operations bottleneck in the IPv6 stack
Date: Wed, 10 Dec 2014 18:58:30 +0100 [thread overview]
Message-ID: <1418234310.24395.5.camel@redhat.com> (raw)
In-Reply-To: <1418231763.24395.2.camel@redhat.com>
On Mi, 2014-12-10 at 18:16 +0100, Hannes Frederic Sowa wrote:
> On Mi, 2014-12-10 at 16:56 +0000, cristian.bercaru@freescale.com wrote:
> >
> > It seems to me that the atomic operations on the IPv6 forwarding path
> > are a bottleneck and they are not scalable with the number of cores.
> > Am I right? What improvements can be brought to the IPv6 kernel code
> > to make it less dependent of atomic operations/variables?
>
> For a starter, something like the following commit:
>
> commit d26b3a7c4b3b26319f18bb645de93eba8f4bdcd5
> Author: Eric Dumazet <edumazet@google.com>
> Date: Tue Jul 31 05:45:30 2012 +0000
>
> ipv4: percpu nh_rth_output cache
Actually, we should be able to remove the atomics in input and
forwarding path by just relying on RCU. I'll have a look.
Bye,
Hannes
prev parent reply other threads:[~2014-12-10 18:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 16:56 atomic operations bottleneck in the IPv6 stack cristian.bercaru
2014-12-10 17:16 ` Hannes Frederic Sowa
2014-12-10 17:58 ` Hannes Frederic Sowa [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=1418234310.24395.5.camel@redhat.com \
--to=hannes@redhat.com \
--cc=R89243@freescale.com \
--cc=Razvan.Ungureanu@freescale.com \
--cc=cristian.bercaru@freescale.com \
--cc=madalin.bucur@freescale.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).