All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Arcangeli <aarcange@redhat.com>
To: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
Cc: Minchan Kim <minchan.kim@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Steven Barrett <damentz@liquorix.net>,
	Ben Gamari <bgamari.foss@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Rik van Riel <riel@redhat.com>, Mel Gorman <mel@csn.ul.ie>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Wu Fengguang <fengguang.wu@intel.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Nick Piggin <npiggin@kernel.dk>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [PATCH v6 0/4] fadvise(DONTNEED) support
Date: Tue, 22 Feb 2011 18:11:58 +0100	[thread overview]
Message-ID: <20110222171158.GC31195@random.random> (raw)
In-Reply-To: <4D63EC77.6070208@mnsu.edu>

On Tue, Feb 22, 2011 at 11:03:51AM -0600, Jeffrey Hundstad wrote:
> On 02/22/2011 07:28 AM, Andrea Arcangeli wrote:
> > Hi Minchan,
> > That's my point, we should check if the "thrashing horribly" is really
> > a "recently" or if it has always happened before with 2.6.18 and previous.
> 
> I would bet that "thrashing" isn't what he meant.  He almost certainly 
> meant "needless I/O" and nothing to do with swapping.  I've seen this 
> similar report before.  This report is almost always gets answered with 
> a "set your swappiness to an appropriate value" type answer.  Or a "your 

Hmm but swappiness can't help if "needless I/O in the morning after
backup" is the problem. So it wouldn't be the right suggestion if
"needless I/O is the problem".

We need a "vmstat 1" during the "trashing horribly"/"needless I/O" in
the morning to be sure.

> userspace app needs to get smarter" type answer.  I think they are 
> trying to do the latter, but need some help from the kernel, and that's 
> what they're trying to do here.

That's fine thing. But I got reports indipendent of this thread from
friends, asking me how to prevent swapping overnight because of
backup, so I connected that report to the above "trashing
horribly"/recently. I had no problems personally but may backup runs
once (not twice to activate/reference pages). I had no time to
investigate this further yet to see if things works ok for me even
with a rsync loop activating and referencing everything.

WARNING: multiple messages have this Message-ID (diff)
From: Andrea Arcangeli <aarcange@redhat.com>
To: Jeffrey Hundstad <jeffrey.hundstad@mnsu.edu>
Cc: Minchan Kim <minchan.kim@gmail.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	linux-mm <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Steven Barrett <damentz@liquorix.net>,
	Ben Gamari <bgamari.foss@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Rik van Riel <riel@redhat.com>, Mel Gorman <mel@csn.ul.ie>,
	KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
	Wu Fengguang <fengguang.wu@intel.com>,
	Johannes Weiner <hannes@cmpxchg.org>,
	Nick Piggin <npiggin@kernel.dk>,
	Balbir Singh <balbir@linux.vnet.ibm.com>,
	KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [PATCH v6 0/4] fadvise(DONTNEED) support
Date: Tue, 22 Feb 2011 18:11:58 +0100	[thread overview]
Message-ID: <20110222171158.GC31195@random.random> (raw)
In-Reply-To: <4D63EC77.6070208@mnsu.edu>

On Tue, Feb 22, 2011 at 11:03:51AM -0600, Jeffrey Hundstad wrote:
> On 02/22/2011 07:28 AM, Andrea Arcangeli wrote:
> > Hi Minchan,
> > That's my point, we should check if the "thrashing horribly" is really
> > a "recently" or if it has always happened before with 2.6.18 and previous.
> 
> I would bet that "thrashing" isn't what he meant.  He almost certainly 
> meant "needless I/O" and nothing to do with swapping.  I've seen this 
> similar report before.  This report is almost always gets answered with 
> a "set your swappiness to an appropriate value" type answer.  Or a "your 

Hmm but swappiness can't help if "needless I/O in the morning after
backup" is the problem. So it wouldn't be the right suggestion if
"needless I/O is the problem".

We need a "vmstat 1" during the "trashing horribly"/"needless I/O" in
the morning to be sure.

> userspace app needs to get smarter" type answer.  I think they are 
> trying to do the latter, but need some help from the kernel, and that's 
> what they're trying to do here.

That's fine thing. But I got reports indipendent of this thread from
friends, asking me how to prevent swapping overnight because of
backup, so I connected that report to the above "trashing
horribly"/recently. I had no problems personally but may backup runs
once (not twice to activate/reference pages). I had no time to
investigate this further yet to see if things works ok for me even
with a rsync loop activating and referencing everything.

--
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-02-22 17:14 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-20 14:43 [PATCH v6 0/4] fadvise(DONTNEED) support Minchan Kim
2011-02-20 14:43 ` Minchan Kim
2011-02-20 14:43 ` [PATCH v6 1/3] deactivate invalidated pages Minchan Kim
2011-02-20 14:43   ` Minchan Kim
2011-02-21  8:29   ` Johannes Weiner
2011-02-21  8:29     ` Johannes Weiner
2011-02-20 14:43 ` [PATCH v6 2/3] memcg: move memcg reclaimable page into tail of inactive list Minchan Kim
2011-02-20 14:43   ` Minchan Kim
2011-02-21  8:40   ` Johannes Weiner
2011-02-21  8:40     ` Johannes Weiner
2011-02-21 14:07     ` Minchan Kim
2011-02-21 14:07       ` Minchan Kim
2011-02-21 15:59     ` Minchan Kim
2011-02-21 15:59       ` Minchan Kim
2011-02-21 16:06       ` Johannes Weiner
2011-02-21 16:06         ` Johannes Weiner
2011-03-28 12:51       ` [PATCH] memcg: fix mem_cgroup_rotate_reclaimable_page Eric Dumazet
2011-03-28 12:51         ` Eric Dumazet
2011-03-28 13:45         ` Minchan Kim
2011-03-28 13:45           ` Minchan Kim
2011-02-20 14:43 ` [PATCH v6 3/3] Reclaim invalidated page ASAP Minchan Kim
2011-02-20 14:43   ` Minchan Kim
2011-02-21 19:07 ` [PATCH v6 0/4] fadvise(DONTNEED) support Andrea Arcangeli
2011-02-21 19:07   ` Andrea Arcangeli
2011-02-21 22:59   ` Minchan Kim
2011-02-21 22:59     ` Minchan Kim
2011-02-22 13:28     ` Andrea Arcangeli
2011-02-22 13:28       ` Andrea Arcangeli
2011-02-22 14:26       ` Minchan Kim
2011-02-22 14:26         ` Minchan Kim
2011-02-22 14:46         ` Andrea Arcangeli
2011-02-22 14:46           ` Andrea Arcangeli
2011-02-22 17:03       ` Jeffrey Hundstad
2011-02-22 17:03         ` Jeffrey Hundstad
2011-02-22 17:11         ` Andrea Arcangeli [this message]
2011-02-22 17:11           ` Andrea Arcangeli

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=20110222171158.GC31195@random.random \
    --to=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=balbir@linux.vnet.ibm.com \
    --cc=bgamari.foss@gmail.com \
    --cc=damentz@liquorix.net \
    --cc=fengguang.wu@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=jeffrey.hundstad@mnsu.edu \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=kosaki.motohiro@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=minchan.kim@gmail.com \
    --cc=npiggin@kernel.dk \
    --cc=peterz@infradead.org \
    --cc=riel@redhat.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 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.