[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87d25hrv9m.fsf@x220.int.ebiederm.org>
Date: Tue, 10 Feb 2015 21:18:13 -0600
From: ebiederm@...ssion.com (Eric W. Biederman)
To: Eric Dumazet <edumazet@...gle.com>
Cc: netdev <netdev@...r.kernel.org>,
Stephen Hemminger <stephen@...workplumber.org>,
Nicolas Dichtel <nicolas.dichtel@...nd.com>,
roopa <roopa@...ulusnetworks.com>,
Hannes Frederic Sowa <hannes@...essinduktion.org>,
Dinesh Dutt <ddutt@...ulusnetworks.com>,
Vipin Kumar <vipin@...ulusnetworks.com>,
Shmulik Ladkani <shmulik.ladkani@...il.com>,
David Ahern <dsahern@...il.com>,
"David S. Miller" <davem@...emloft.net>
Subject: Re: network namespace bloat
Eric Dumazet <edumazet@...gle.com> writes:
> On Tue, Feb 10, 2015 at 6:42 PM, Eric W. Biederman
> <ebiederm@...ssion.com> wrote:
>
>>
>> Those large hash tables impact creation speed as large memory
>> allocations require more work from the memory allocators, and they
>> affect reliability of as order > 0 pages are not reliabily available in
>> the kernel. So from a network namespace perspective I would really like
>> to convert the per network namespace hash tables to hash tables that
>> have a single instance across all network namespaces.
>>
>
> tcp_metric can fallback to vzalloc() after commit 976a702ac9eea ?
True, although vmalloc space is limited on some architectures.
> There is nothing preventing to use a single tcp_metric, a bit like
> global TCP hash table.
>
> We only have to convert the thing...
Thanks for the confirmation, that is what I figured was going on.
> Note : At Google we do not save tcp metrics.
> We have to use it only for FastOpen cookies eventually (For clients)
Interesting. That makes it doubly desirable to not need to allocate
a per network namespace hash table.
Eric
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists