From: KOSAKI Motohiro <kosaki.motohiro@gmail.com>
To: Rik van Riel <riel@redhat.com>
Cc: linux-mm@kvack.org, aarcange@redhat.com,
linux-kernel@vger.kernel.org, Mel Gorman <mel@csn.ul.ie>,
akpm@linux-foundation.org, Johannes Weiner <hannes@cmpxchg.org>,
hughd@google.com
Subject: Re: [PATCH -mm 2/2] mm: kswapd carefully invoke compaction
Date: Wed, 11 Jan 2012 14:57:25 -0500 [thread overview]
Message-ID: <CAHGf_=qJv99TbF2eNosbeHU5pzk2e3mDer0u2U+EsXdf2p5_Aw@mail.gmail.com> (raw)
In-Reply-To: <4F0D8FCE.7080202@redhat.com>
> I believe we do need some background compaction, especially
> to help allocations from network interrupts.
I completely agree.
> If you believe the compaction is better done from some
> other thread, I guess we could do that, but truthfully, if
> kswapd spends a lot of time doing compaction, I made a
> mistake somewhere :)
I don't have much experience of compaction on real production systems.
but I have a few bad experience of background lumpy reclaim. If much
network allocation is happen when kswapd get stucked large order lumpy
reclaim, kswapd can't work for making order-0 job.it was bad. I'm only
worry about similar issue will occur.
But, ok, we can fix it when we actually observed such thing. So,
please go ahead.
--
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>
next prev parent reply other threads:[~2012-01-11 19:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 2:31 [PATCH -mm 0/2] kswapd vs compaction improvements Rik van Riel
2012-01-10 2:33 ` [PATCH -mm 1/2] mm: kswapd test order 0 watermarks when compaction is enabled Rik van Riel
2012-01-12 15:46 ` Mel Gorman
2012-01-10 2:33 ` [PATCH -mm 2/2] mm: kswapd carefully invoke compaction Rik van Riel
2012-01-11 7:25 ` KOSAKI Motohiro
2012-01-11 13:34 ` Rik van Riel
2012-01-11 19:57 ` KOSAKI Motohiro [this message]
2012-01-12 16:12 ` Mel Gorman
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='CAHGf_=qJv99TbF2eNosbeHU5pzk2e3mDer0u2U+EsXdf2p5_Aw@mail.gmail.com' \
--to=kosaki.motohiro@gmail.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox