mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@osdl.org>
To: Robin Holt <holt@sgi.com>
Cc: peterc@gelato.unsw.edu.au, holt@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: vm_dirty_ratio seems a bit large.
Date: Fri, 18 Mar 2005 11:16:39 -0800	[thread overview]
Message-ID: <20050318111639.24b007f7.akpm@osdl.org> (raw)
In-Reply-To: <20050318123112.GA28473@lnx-holt.americas.sgi.com>

Robin Holt <holt@sgi.com> wrote:
>
> > No, you could just extend them to understand fixed point.  Keep
>  > printing integers as integers, print non-integers with one (or two:
>  > will we ever need 0.01% increments?) decimal places.
> 
>  Right now, it is possible to build our largest Altix configuration with
>  64TB of memory (unfortunatetly, we can't get any customers to pay that
>  large of bill ;).  We are currently shipping a few 4TB systems and hope
>  to be selling 20TB systems by the end of the year (at least engineering
>  hopes to).
> 
>  Given that, two decimal places are really not enough.  We probably need
>  at least 3.
> 
>  Is there any reason to not do 3 places?  Is this the right direction to
>  head or does anybody know of problems this would cause?

It's a rather unorthodox fix, but not illogical.  I guess it depends upon
how much sysctl infrastructure it adds.  Probably quite a lot.

Another approach would be to just say the ratio now has a range 0 .. 
999,999 and then, if it happens to be less than 100, treat that as a
percentage for back-compatibility reasons.  Although that's a bit kludgy
and perhaps a completely new /proc entry would be better.


      reply	other threads:[~2005-03-18 19:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 20:52 Robin Holt
2005-03-17 21:31 ` Andrew Morton
2005-03-17 22:27   ` Peter Chubb
2005-03-18 12:31     ` Robin Holt
2005-03-18 19:16       ` Andrew Morton [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=20050318111639.24b007f7.akpm@osdl.org \
    --to=akpm@osdl.org \
    --cc=holt@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterc@gelato.unsw.edu.au \
    /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

all inboxes | Powered by JetHome®