From: Yann Dupont <Yann.Dupont@univ-nantes.fr>
To: Mark Tinguely <tinguely@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: kernels 3.4 slower due to allocation workqueue
Date: Wed, 17 Apr 2013 16:35:28 +0200 [thread overview]
Message-ID: <516EB330.8050207@univ-nantes.fr> (raw)
In-Reply-To: <516EADA5.1040007@sgi.com>
Le 17/04/2013 16:11, Mark Tinguely a écrit :
> On 04/17/13 08:44, Yann Dupont wrote:
>> Le 16/04/2013 15:26, Mark Tinguely a écrit :
>>>
>>> The filesystem can hang but only if the OS cannot allocate another
>>> worker when doing certain calls.
>>>
>>> --Mark.
>>
>> Ok, any chance to see these fixes backported to 3.4 ?
>>
>> Cheers,
>>
>
> All of the patches apply to Linux 3.4 without modification.
Yes, sorry, I should have said incorporated/pushed back
>
> It does not sound like the patches will be pushed back to stable at
> this time.
If you consider, for the moment, not pushing the patches in 3.4,
(because of stability concerns, or you judge these patches intrusives,
or whatever good reason), I won't do either, because I have no vision of
the potential problems with the patched kernel. I always try to stay on
pure vanilla kernels, longterm if possible, because stability is the
more important.
My best bet is probably 3.8 kernels right now (even if they are not
longterm), or maybe simply going back to 3.2.
Thanks for your answers,
Cheers
--
Yann Dupont - Service IRTS, DSI Université de Nantes
Tel : 02.53.48.49.20 - Mail/Jabber : Yann.Dupont@univ-nantes.fr
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-04-17 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-15 9:39 kernels 3.4 slower due to allocation workqueue Yann Dupont
2013-04-15 13:45 ` Mark Tinguely
2013-04-16 7:24 ` Yann Dupont
2013-04-16 8:37 ` Yann Dupont
2013-04-16 13:26 ` Mark Tinguely
2013-04-17 13:44 ` Yann Dupont
2013-04-17 14:11 ` Mark Tinguely
2013-04-17 14:35 ` Yann Dupont [this message]
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=516EB330.8050207@univ-nantes.fr \
--to=yann.dupont@univ-nantes.fr \
--cc=tinguely@sgi.com \
--cc=xfs@oss.sgi.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