From: Peter Zijlstra <peterz@infradead.org>
To: Ryan Hope <rmh3093@gmail.com>
Cc: linux-mm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Nick Piggin <nickpiggin@yahoo.com.au>
Subject: Re: [BUG] Lockless patches cause hardlock under heavy IO
Date: Thu, 19 Jun 2008 10:12:02 +0200 [thread overview]
Message-ID: <1213863122.16944.257.camel@twins> (raw)
In-Reply-To: <48f7fe350806181415l4eba61b3i1d206de03147575e@mail.gmail.com>
On Wed, 2008-06-18 at 17:15 -0400, Ryan Hope wrote:
> I applied the following patches from 2.6-26-rc5-mm3 to 2.6.26-rc6 and
> they caused a hardlock under heavy IO:
What kind of machine, how much memory, how many spindles, what
filesystem and what is heavy load?
Furthermore, try the NMI watchdog with serial/net-console to capture its
output.
> x86-implement-pte_special.patch
> mm-introduce-get_user_pages_fast.patch
> mm-introduce-get_user_pages_fast-fix.patch
> mm-introduce-get_user_pages_fast-checkpatch-fixes.patch
> x86-lockless-get_user_pages_fast.patch
> x86-lockless-get_user_pages_fast-checkpatch-fixes.patch
> x86-lockless-get_user_pages_fast-fix.patch
> x86-lockless-get_user_pages_fast-fix-2.patch
> x86-lockless-get_user_pages_fast-fix-2-fix-fix.patch
> x86-lockless-get_user_pages_fast-fix-warning.patch
> dio-use-get_user_pages_fast.patch
> splice-use-get_user_pages_fast.patch
> x86-support-1gb-hugepages-with-get_user_pages_lockless.patch
> #
> mm-readahead-scan-lockless.patch
> radix-tree-add-gang_lookup_slot-gang_lookup_slot_tag.patch
> #mm-speculative-page-references.patch: clameter saw bustage
> mm-speculative-page-references.patch
> mm-speculative-page-references-fix.patch
> mm-speculative-page-references-fix-fix.patch
> mm-speculative-page-references-hugh-fix3.patch
> mm-lockless-pagecache.patch
> mm-spinlock-tree_lock.patch
> powerpc-implement-pte_special.patch
>
> I am on an x86_64. I dont know what other info you need...
next prev parent reply other threads:[~2008-06-19 8:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 21:15 [BUG] Lockless patches cause hardlock under heavy IO Ryan Hope
2008-06-18 21:28 ` Arjan van de Ven
2008-06-19 14:45 ` Ryan Hope
2008-06-20 0:05 ` Arjan van de Ven
2008-06-19 8:12 ` Peter Zijlstra [this message]
2008-06-19 8:19 ` Nick Piggin
2008-06-19 14:52 ` Ryan Hope
2008-06-19 20:31 ` Ryan Hope
2008-06-20 14:33 ` Ryan Hope
2008-06-22 14:37 ` Ryan Hope
2008-06-22 15:07 ` Peter Zijlstra
2008-06-22 15:18 ` Ryan Hope
2008-06-23 2:29 ` Nick Piggin
2008-06-23 3:51 ` Ryan Hope
2008-06-23 3:56 ` Nick Piggin
2008-06-23 11:54 ` Nick Piggin
2008-06-23 13:05 ` Paul E. McKenney
2008-06-24 0:13 ` Nick Piggin
2008-06-24 15:12 ` Ryan Hope
2008-06-24 15:32 ` Paul E. McKenney
2008-06-24 15:57 ` Ryan Hope
2008-06-24 16:12 ` Paul E. McKenney
2008-06-24 16:23 ` Ryan Hope
2008-06-24 18:01 ` Ryan Hope
2008-06-23 23:48 ` Zan Lynx
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=1213863122.16944.257.camel@twins \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=nickpiggin@yahoo.com.au \
--cc=rmh3093@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 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.