mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yaroslav Halchenko <yoh@psychology.rutgers.edu>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: kswapd/tg3 issue
Date: Thu, 30 Nov 2006 10:28:51 -0500	[thread overview]
Message-ID: <20061130152851.GN2021@washoe.onerussian.com> (raw)
In-Reply-To: <1164899853.3233.19.camel@laptopd505.fenrus.org>

Thank you Arjan for advice

I had 5746, made it 8619.

Is that a good practice in general to have that value higher for a
server with lots of I/O including networking? (there is a RAID on that
system and 2 bonded gigabit interfaces) Is there any heuristic to decide
on that value ?

On Thu, 30 Nov 2006, Arjan van de Ven wrote:

> >...<

> actually since this was networking...
> you probably should bump the value in
> /proc/sys/vm/min_free_kbytes
> a bit (like by 50%); that makes the kernel keep a bigger pool free for
> emergencies/spikes...
> That might be enough already if your system isn't swapping a whole lot.
-- 
Yaroslav Halchenko
Research Assistant, Psychology Department, Rutgers-Newark
Student  Ph.D. @ CS Dept. NJIT
Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171
        101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102
WWW:     http://www.linkedin.com/in/yarik        

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

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-30 14:43 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 [this message]
2006-11-30 15:39     ` Alan
2006-11-30 15:45       ` Avi Kivity
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=20061130152851.GN2021@washoe.onerussian.com \
    --to=yoh@psychology.rutgers.edu \
    --cc=linux-kernel@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
all inboxes | Powered by JetHome®