linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Zhu Yanhai <zhu.yanhai@gmail.com>
Cc: Wu Fengguang <fengguang.wu@intel.com>,
	Pekka Enberg <penberg@kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mel Gorman <mel@csn.ul.ie>, Jens Axboe <jaxboe@fusionio.com>,
	Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: slow performance on disk/network i/o full speed after drop_caches
Date: Wed, 31 Aug 2011 09:11:02 +0200	[thread overview]
Message-ID: <4E5DDE86.3040202@profihost.ag> (raw)
In-Reply-To: <4E573A99.4060309@profihost.ag>

Hi Fengguang,
Hi Yanhai,

> you're abssolutely corect zone_reclaim_mode is on - but why?
> There must be some linux software which switches it on.
>
> ~# grep 'zone_reclaim_mode' /etc/sysctl.* -r -i
> ~#
>
> also
> ~# grep 'zone_reclaim_mode' /etc/sysctl.* -r -i
> ~#
>
> tells us nothing.
>
> I've then read this:
>
> "zone_reclaim_mode is set during bootup to 1 if it is determined that
> pages from remote zones will cause a measurable performance reduction.
> The page allocator will then reclaim easily reusable pages (those page
> cache pages that are currently not used) before allocating off node pages."
>
> Why does the kernel do that here in our case on these machines.

Can nobody help why the kernel in this case set it to 1?

Stefan

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-08-31  7:11 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4E5494D4.1050605@profihost.ag>
2011-08-24  6:20 ` slow performance on disk/network i/o full speed after drop_caches Pekka Enberg
2011-08-24  9:01   ` Stefan Priebe - Profihost AG
2011-08-24  9:33     ` Wu Fengguang
2011-08-25  9:00       ` Stefan Priebe - Profihost AG
2011-08-26  2:16         ` Wu Fengguang
2011-08-26  2:54           ` Stefan Priebe - Profihost AG
2011-08-26  3:03             ` Wu Fengguang
2011-08-26  3:13               ` Stefan Priebe
2011-08-26  3:26                 ` Wu Fengguang
2011-08-26  3:30                   ` Zhu Yanhai
2011-08-26  6:18                     ` Stefan Priebe - Profihost AG
2011-08-31  7:11                       ` Stefan Priebe - Profihost AG [this message]
2011-09-01  4:14                         ` Wu Fengguang
2011-09-01  5:41                           ` Stefan Priebe - Profihost AG
2011-09-01 12:57                           ` Mel Gorman
2011-08-24  9:32   ` Wu Fengguang

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=4E5DDE86.3040202@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=jaxboe@fusionio.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=netdev@vger.kernel.org \
    --cc=penberg@kernel.org \
    --cc=zhu.yanhai@gmail.com \
    /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).