From: John Heffner <jheffner@psc.edu>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] fix up sysctl_tcp_mem initialization
Date: Wed, 15 Nov 2006 12:46:00 -0500 [thread overview]
Message-ID: <455B5258.5090504@psc.edu> (raw)
In-Reply-To: <20061114.203118.35665382.davem@davemloft.net>
David Miller wrote:
>> However, I wonder if we want to set this differently than the way this
>> patch does it. Depending on how far off the memory size is from a power
>> of two (exactly equal to a power of two is the worst case), and if total
>> memory <128M, it can be substantially less than 3/4.
>
> Longer term, yes, probably a better way exists.
>
> So you concern is that when we round to a power of 2 like we do
> now, we often mis-shoot?
I'm not that concerned about it, but basically yes, there are big (x2)
jumps on power-of-two memory size boundaries. There's also a bigger
(x8) discontinuity at 128k pages. It could be smoother.
-John
prev parent reply other threads:[~2006-11-15 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 20:02 [PATCH] fix up sysctl_tcp_mem initialization John Heffner
2006-11-15 4:31 ` David Miller
2006-11-15 17:46 ` John Heffner [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=455B5258.5090504@psc.edu \
--to=jheffner@psc.edu \
--cc=davem@davemloft.net \
--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).