From: Mark Tinguely <tinguely@sgi.com>
To: Yann Dupont <Yann.Dupont@univ-nantes.fr>
Cc: xfs@oss.sgi.com
Subject: Re: kernels 3.4 slower due to allocation workqueue
Date: Wed, 17 Apr 2013 09:11:49 -0500 [thread overview]
Message-ID: <516EADA5.1040007@sgi.com> (raw)
In-Reply-To: <516EA72F.3030200@univ-nantes.fr>
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.
It does not sound like the patches will be pushed back to stable at this
time.
--Mark.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-04-17 14:11 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 [this message]
2013-04-17 14:35 ` Yann Dupont
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=516EADA5.1040007@sgi.com \
--to=tinguely@sgi.com \
--cc=Yann.Dupont@univ-nantes.fr \
--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