From: Stephen Hemminger <shemminger@vyatta.com>
To: Mihai Maruseac <mihai.maruseac@gmail.com>
Cc: davem@davemloft.net, eric.dumazet@gmail.com,
kuznet@ms2.inr.ac.ru, jmorris@namei.org, yoshfuji@linux-ipv6.org,
kaber@trash.net, netdev@vger.kernel.org,
Mihai Maruseac <mmaruseac@ixiacom.com>,
Daniel Baluta <dbaluta@ixiacom.com>
Subject: Re: [PATCH] ipv6/addrconf: speedup /proc/net/if_inet6 filling
Date: Wed, 4 Jan 2012 08:22:00 -0800 [thread overview]
Message-ID: <20120104082200.437df26a@nehalam.linuxnetplumber.net> (raw)
In-Reply-To: <1325669495-5626-1-git-send-email-mmaruseac@ixiacom.com>
On Wed, 4 Jan 2012 11:31:35 +0200
Mihai Maruseac <mihai.maruseac@gmail.com> wrote:
> This ensures a linear behaviour when filling /proc/net/if_inet6 thus making
> ifconfig run really fast on IPv6 only addresses. In fact, with this patch and
> the IPv4 one sent a while ago, ifconfig will run in linear time regardless of
> address type.
>
> IPv4 related patch: f04565ddf52e401880f8ba51de0dff8ba51c99fd
> dev: use name hash for dev_seq_ops
> ...
>
> Some statistics (running ifconfig > /dev/null on a different setup):
>
> iface count / IPv6 no-patch time / IPv6 patched time / IPv4 time
> ----------------------------------------------------------------
> 6250 | 0.23 s | 0.13 s | 0.11 s
> 12500 | 0.62 s | 0.28 s | 0.22 s
> 25000 | 2.91 s | 0.57 s | 0.46 s
> 50000 | 11.37 s | 1.21 s | 0.94 s
> 128000 | 86.78 s | 3.05 s | 2.54 s
>
> Signed-off-by: Mihai Maruseac <mmaruseac@ixiacom.com>
> Cc: Daniel Baluta <dbaluta@ixiacom.com>
> ---
> net/ipv6/addrconf.c | 43 ++++++++++++++++++++++++++++---------------
> 1 files changed, 28 insertions(+), 15 deletions(-)
>
What about netlink? Also ifconfig is really considered deprecated,
especially for ipv6 usage.
next prev parent reply other threads:[~2012-01-04 16:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-04 9:31 [PATCH] ipv6/addrconf: speedup /proc/net/if_inet6 filling Mihai Maruseac
2012-01-04 16:22 ` Stephen Hemminger [this message]
2012-01-04 17:03 ` Mihai Maruseac
2012-01-05 14:07 ` Mihai Maruseac
2012-01-04 21: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=20120104082200.437df26a@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=dbaluta@ixiacom.com \
--cc=eric.dumazet@gmail.com \
--cc=jmorris@namei.org \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=mihai.maruseac@gmail.com \
--cc=mmaruseac@ixiacom.com \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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 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.