From: Benjamin LaHaise <bcrl@lhnet.ca>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Octavian Purdila <opurdila@ixiacom.com>,
netdev@vger.kernel.org, Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: [PATCH 2/2] ipv4: factorize cache clearing for batched unregister operations
Date: Mon, 16 Nov 2009 19:22:38 -0500 [thread overview]
Message-ID: <20091117002238.GH12422@kvack.org> (raw)
In-Reply-To: <20091116160646.39c0a1ac@nehalam>
On Mon, Nov 16, 2009 at 04:06:46PM -0800, Stephen Hemminger wrote:
> And what about IPV6?
It's not possible to create more than a few thousand IPv6 interfaces in
my tests with a 4GB vm. The culprit seems to be the per-cpu arrays for
statistics using vmalloc() and wasting gobs of memory as a result (memory
usage seems to be 10x per interface vs what IPv4 is using), but I haven't
dug too deeply yet.
-ben
next prev parent reply other threads:[~2009-11-17 0:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-16 23:49 [PATCH 2/2] ipv4: factorize cache clearing for batched unregister operations Octavian Purdila
2009-11-17 0:06 ` Stephen Hemminger
2009-11-17 0:22 ` Benjamin LaHaise [this message]
2009-11-17 8:35 ` David Miller
2009-11-17 7:22 ` Octavian Purdila
2009-11-17 8:34 ` David Miller
2009-11-18 13:04 ` 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=20091117002238.GH12422@kvack.org \
--to=bcrl@lhnet.ca \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.com \
--cc=shemminger@vyatta.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 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).