From: Kirill Korotaev <dev@sw.ru>
To: akepner@sgi.com
Cc: David Miller <davem@davemloft.net>,
ak@suse.de, kuznet@ms2.inr.ac.ru, netdev@vger.kernel.org
Subject: Re: [PATCH] limit rt cache size
Date: Wed, 09 Aug 2006 12:05:33 +0400 [thread overview]
Message-ID: <44D9974D.9010408@sw.ru> (raw)
In-Reply-To: <Pine.LNX.4.61.0608081707410.2452@localhost.localdomain>
>> 1) dynamic table growth is the only reasonable way to
>> handle this and not waste memory in all cases
>> ....
>
>
> Definitely that's the ideal way to go.
>
> But there's alot of state to update (more or less
> atomically, too) in the TCP hashes. Looks tricky to
> do that without hurting performance, especially since
> you'll probably want to resize the tables when you've
> discovered they're full and busy....
and the memory if fragmented too! :/
Kirill
next prev parent reply other threads:[~2006-08-09 8:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <44D75EF8.1070901@sw.ru>
2006-08-07 16:48 ` [PATCH] limit rt cache size Alexey Kuznetsov
2006-08-08 3:42 ` David Miller
2006-08-08 5:11 ` Andi Kleen
2006-08-08 6:18 ` David Miller
2006-08-08 6:53 ` Andi Kleen
2006-08-08 7:01 ` David Miller
2006-08-08 12:54 ` Kirill Korotaev
2006-08-08 12:58 ` Andi Kleen
2006-08-08 20:37 ` akepner
2006-08-08 23:23 ` Andi Kleen
2006-08-09 0:06 ` akepner
2006-08-09 0:11 ` David Miller
2006-08-09 0:11 ` akepner
2006-08-09 0:22 ` David Miller
2006-08-09 1:02 ` Andi Kleen
2006-08-09 16:16 ` akepner
2006-08-09 16:32 ` Andi Kleen
2006-08-10 0:02 ` David Miller
2006-08-09 8:05 ` Kirill Korotaev [this message]
2006-08-09 0:24 ` Andi Kleen
2006-08-09 0:32 ` David Miller
2006-08-09 8:09 ` Kirill Korotaev
2006-08-09 8:53 ` Eric Dumazet
2006-08-09 9:22 ` David Miller
2006-08-08 8:17 ` Kirill Korotaev
2006-08-08 8:34 ` David Miller
2006-08-08 8:57 ` Eric Dumazet
2006-08-08 9:12 ` 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=44D9974D.9010408@sw.ru \
--to=dev@sw.ru \
--cc=ak@suse.de \
--cc=akepner@sgi.com \
--cc=davem@davemloft.net \
--cc=kuznet@ms2.inr.ac.ru \
--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).