From: Andrea Arcangeli <aarcange@redhat.com>
To: Dave Jones <davej@redhat.com>, Mel Gorman <mgorman@suse.de>,
Johannes Weiner <jweiner@redhat.com>, Jan Kara <jack@suse.cz>,
Andy Isaacson <adi@hexapodia.org>,
linux-kernel@vger.kernel.org, linux-mm@vger.kernel.org,
kernel-team@fedoraproject.org
Subject: Re: long sleep_on_page delays writing to slow storage
Date: Thu, 17 Nov 2011 23:53:54 +0100 [thread overview]
Message-ID: <20111117225354.GL3306@redhat.com> (raw)
In-Reply-To: <20111117194719.GA23213@redhat.com>
Hi Dave,
On Thu, Nov 17, 2011 at 02:47:20PM -0500, Dave Jones wrote:
> When I build a kernel on my laptop, when it gets to the final link stage,
> and there's a ton of IO, my entire X session wedges for a few seconds.
> This may be unrelated, because this is on an SSD, which shouldn't suffer
> from the slow IO of the USB devices mentioned in this thread.
>
> (This is even with that patch applied btw, perhaps adding further fuel to
> the idea that it's unrelated).
Agreed, if it happens even with the patch applied it's most certainly
not related to compaction. Maybe more IO scheduler related, or
something like that. You can also try to set
transparent_hugepage/defrag to "never" to be sure, then compaction
won't run.
next prev parent reply other threads:[~2011-11-17 22:54 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 4:59 long sleep_on_page delays writing to slow storage Andy Isaacson
2011-11-09 17:00 ` Jan Kara
2011-11-09 17:52 ` Mel Gorman
2011-11-09 18:06 ` Andrea Arcangeli
2011-11-10 0:53 ` Mel Gorman
2011-11-10 1:54 ` Andrea Arcangeli
2011-11-10 9:34 ` Johannes Weiner
2011-11-14 18:47 ` Dave Jones
2011-11-15 10:13 ` Mel Gorman
2011-11-17 19:47 ` Dave Jones
2011-11-17 22:53 ` Andrea Arcangeli [this message]
2011-11-18 11:11 ` Mel Gorman
2011-11-18 12:19 ` Josh Boyer
2011-11-21 9:18 ` Johannes Weiner
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=20111117225354.GL3306@redhat.com \
--to=aarcange@redhat.com \
--cc=adi@hexapodia.org \
--cc=davej@redhat.com \
--cc=jack@suse.cz \
--cc=jweiner@redhat.com \
--cc=kernel-team@fedoraproject.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=mgorman@suse.de \
/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.