From: Thomas Gleixner <tglx@linutronix.de>
To: Jan de Kruyf <jan.de.kruyf@gmail.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Filesystem lockup with CONFIG_PREEMPT_RT
Date: Mon, 7 Jul 2014 15:00:37 +0200 (CEST) [thread overview]
Message-ID: <alpine.DEB.2.10.1407071458330.22031@nanos> (raw)
In-Reply-To: <CAA85NCgJPczdQ0mhH3n6cwuZ0kTT-ZFayn3RAjpGAJOB3AM47g@mail.gmail.com>
On Mon, 7 Jul 2014, Jan de Kruyf wrote:
> Hope I do not kick in an open door, but
>
> Linux JanDell 3.2.0-0.bpo.3-rt-686-pae #1 SMP PREEMPT RT Thu Aug 23
> 09:55:27 UTC 2012 i686 GNU/Linux
> and
> Linux jan 3.2.0-4-rt-amd64 #1 SMP PREEMPT RT Debian 3.2.57-3+deb7u2
> x86_64 GNU/Linux
>
> does not give the same problem that I experienced with XFS.
> So there is a hickup between version 3.2-rt and 3.10-rt I would say.
There is no hickup. Just stuff changes over time and makes certain
problems more likely/obvious.
The workqueue issue has been there since we had to deal with the
workqueue wakeup from the guts of the scheduler.
Thanks,
tglx
next prev parent reply other threads:[~2014-07-07 13:00 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-07 8:48 Filesystem lockup with CONFIG_PREEMPT_RT Jan de Kruyf
2014-07-07 13:00 ` Thomas Gleixner [this message]
2014-07-07 16:23 ` Austin Schuh
2014-07-08 8:03 ` Jan de Kruyf
2014-07-08 16:09 ` Austin Schuh
-- strict thread matches above, loose matches on Subject: below --
2014-07-05 19:30 Jan de Kruyf
2014-05-21 19:30 John Blackwood
2014-05-21 19:30 ` John Blackwood
2014-05-21 21:59 ` Austin Schuh
2014-05-21 21:59 ` Austin Schuh
2014-07-05 20:36 ` Thomas Gleixner
2014-07-05 20:36 ` Thomas Gleixner
2014-05-14 2:29 Austin Schuh
2014-05-14 2:29 ` Austin Schuh
2014-05-21 6:23 ` Austin Schuh
2014-05-21 6:23 ` Austin Schuh
2014-05-21 7:33 ` Richard Weinberger
2014-05-21 7:33 ` Richard Weinberger
2014-06-26 19:50 ` Austin Schuh
2014-06-26 22:35 ` Thomas Gleixner
2014-06-27 0:07 ` Austin Schuh
2014-06-27 3:22 ` Mike Galbraith
2014-06-27 12:57 ` Mike Galbraith
2014-06-27 14:01 ` Steven Rostedt
2014-06-27 17:34 ` Mike Galbraith
2014-06-27 17:54 ` Steven Rostedt
2014-06-27 18:07 ` Mike Galbraith
2014-06-27 18:19 ` Steven Rostedt
2014-06-27 19:11 ` Mike Galbraith
2014-06-28 1:18 ` Austin Schuh
2014-06-28 3:32 ` Mike Galbraith
2014-06-28 6:20 ` Austin Schuh
2014-06-28 7:11 ` Mike Galbraith
2014-06-27 14:24 ` Thomas Gleixner
2014-06-28 4:51 ` Mike Galbraith
2014-07-01 0:12 ` Austin Schuh
2014-07-01 0:53 ` Austin Schuh
2014-07-05 20:26 ` Thomas Gleixner
2014-07-06 4:55 ` Austin Schuh
2014-07-01 3:01 ` Austin Schuh
2014-07-01 19:32 ` Austin Schuh
2014-07-03 23:08 ` Austin Schuh
2014-07-04 4:42 ` Mike Galbraith
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=alpine.DEB.2.10.1407071458330.22031@nanos \
--to=tglx@linutronix.de \
--cc=jan.de.kruyf@gmail.com \
--cc=linux-rt-users@vger.kernel.org \
/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.