From: "Seth, Rohit" <rohit.seth@intel.com>
From: Mel Gorman Sent: Tuesday, November 22, 2005 11:18 AM
To: Mel Gorman <mel@csn.ul.ie>, linux-mm@kvack.org
Cc: nickpiggin@yahoo.com.au, ak@suse.de,
linux-kernel@vger.kernel.org, lhms-devel@lists.sourceforge.net,
mingo@elte.hu
Subject: RE: [PATCH 5/5] Light fragmentation avoidance without usemap: 005_drainpercpu
Date: Tue, 22 Nov 2005 15:43:33 -0800 [thread overview]
Message-ID: <01EF044AAEE12F4BAAD955CB75064943053DF65D@scsmsx401.amr.corp.intel.com> (raw)
>Per-cpu pages can accidentally cause fragmentation because they are
free, >but
>pinned pages in an otherwise contiguous block. When this patch is
applied,
>the per-cpu caches are drained after the direct-reclaim is entered if
the
I don't think this is the right place to drain the pcp. Since direct
reclaim is already done, so it is possible that allocator can service
the request without draining the pcps.
>requested order is greater than 3.
Why this order limit. Most of the previous failures seen (because of my
earlier patches of bigger and more physical contiguous chunks for pcps)
were with order 1 allocation.
>It simply reuses the code used by suspend
>and hotplug and only is triggered when anti-defragmentation is enabled.
>
That code has issues with pre-emptible kernel.
I will be shortly sending the patch to free pages from pcp when higher
order
allocation is not able to get serviced from global list.
-rohi
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2005-11-22 23:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-22 23:43 Seth, Rohit, Tuesday, November [this message]
2005-11-23 0:17 ` Mel Gorman
2005-11-23 1:22 ` Rohit Seth
2005-11-23 8:33 ` Mel Gorman
-- strict thread matches above, loose matches on Subject: below --
2005-11-22 19:17 [PATCH 0/5] Light fragmentation avoidance without usemap Mel Gorman
2005-11-22 19:17 ` [PATCH 5/5] Light fragmentation avoidance without usemap: 005_drainpercpu 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=01EF044AAEE12F4BAAD955CB75064943053DF65D@scsmsx401.amr.corp.intel.com \
--to=rohit.seth@intel.com \
--cc=ak@suse.de \
--cc=lhms-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
/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