All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@argo.co.il>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: Yaroslav Halchenko <yoh@psychology.rutgers.edu>,
	linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: kswapd/tg3 issue
Date: Thu, 30 Nov 2006 17:45:35 +0200	[thread overview]
Message-ID: <456EFC9F.9060607@argo.co.il> (raw)
In-Reply-To: <20061130153906.59d78223@localhost.localdomain>

Alan wrote:
> Under heavy network or I/O pressure it may not have time to swap to get
> the memory. Thus adding swap won't usually help. Adding RAM may do but
> its often not the best answer. Arjan's suggestion should sort it, and -
> yes typically boxes with very high I/O and network load need more of a
> pool of memory free for immediate use than other systems.
>   

It could be nice if the kernel could autotune this, for example by 
raising the free memory goal when memory shortage is detected, and 
lowering it gradually when not.

The sysctl could be a minimum from which this is calculated.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2006-11-30 15:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30 14:43 kswapd/tg3 issue Yaroslav Halchenko
2006-11-30 15:04 ` Alan
2006-11-30 15:10   ` Yaroslav Halchenko
2006-11-30 15:17     ` Arjan van de Ven
2006-11-30 15:28       ` Yaroslav Halchenko
2006-11-30 15:39     ` Alan
2006-11-30 15:45       ` Avi Kivity [this message]
2006-11-30 16:28         ` Yaroslav Halchenko
2006-12-01  6:19   ` Herbert Xu
2006-12-01 14:08     ` Yaroslav Halchenko

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=456EFC9F.9060607@argo.co.il \
    --to=avi@argo.co.il \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yoh@psychology.rutgers.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.