public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 16 Apr 2013 09:24:40 +0200	[thread overview]
Message-ID: <516CFCB8.1060804@univ-nantes.fr> (raw)
In-Reply-To: <516C046C.8080908@sgi.com>

Le 15/04/2013 15:45, Mark Tinguely a écrit :
>
> Here are the allocation worker changes.
>

Hello mark,  thanks for you answer

> The biggest performance commit should be aa292847, which limits the 
> callers to the worker.
>
> commit 3b876c8f2a361ceeed3fed894980c69066f903a0
> Author: Jeff Liu <jeff.liu@oracle.com>
> Date:   Thu Jun 7 15:44:32 2012 +0800
>
>     xfs: fix debug_object WARN at xfs_alloc_vextent()
>
> commit aa292847b9fc6e187547110de833a7d3131bbddf
> Author: Dave Chinner <dchinner@redhat.com>
> Date:   Thu Jul 12 07:40:43 2012 +1000
>
>     xfs: don't defer metadata allocation to the workqueue
>

Only These 2 commits are candidates, the others are post 3.5.
I'll try to patch a 3.4 with each patch.

>  commit 2455881c0b52f87be539c4c7deab1afff4d8a560
> Author: Dave Chinner <dchinner@redhat.com>
> Date:   Fri Oct 5 11:06:58 2012 +1000
>
>     xfs: introduce XFS_BMAPI_STACK_SWITCH
>
> commit e04426b9202bccd4cfcbc70b2fa2aeca1c86d8f5
> Author: Dave Chinner <dchinner@redhat.com>
> Date:   Fri Oct 5 11:06:59 2012 +1000
>
>     xfs: move allocation stack switch up to xfs_bmapi_allocate
>
> commit 9e96fe6df44425b69ed89f6ac20352cec1f127d7
> Author: Brian Foster <bfoster@redhat.com>
> Date:   Thu Jan 17 13:11:29 2013 -0500
>
>     xfs: pull up stack_switch check into xfs_bmapi_write
>
>
> The last 3 patches address an AGF buffer hang with the allocation worker.
>
> --Mark.

As 3.4 Kernels don't have thoses patches, is there a risk associated 
with  3.4 kernels ?

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

  reply	other threads:[~2013-04-16  7:24 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 [this message]
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

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=516CFCB8.1060804@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