From: Dave Chinner <david@fromorbit.com>
To: Tru Huynh <tru@pasteur.fr>
Cc: Subranshu Patel <spatel.ml@gmail.com>, xfs@oss.sgi.com
Subject: Re: High %user CPU in XFS
Date: Mon, 18 Feb 2013 08:29:32 +1100 [thread overview]
Message-ID: <20130217212932.GZ26694@dastard> (raw)
In-Reply-To: <20130217210408.GH2513@sillage.bis.pasteur.fr>
On Sun, Feb 17, 2013 at 10:04:08PM +0100, Tru Huynh wrote:
> On Sun, Feb 17, 2013 at 09:20:46PM +0530, Subranshu Patel wrote:
> > I created 2 filesystem on my system (RHEL 6.3, kernel 2.6.32) - XFS
> > and EXT4 and mounted them.
> probably:
> https://bugzilla.redhat.com/show_bug.cgi?id=883905
Definitely not. That's an idle condition issue and does not
increase CPU usage at all.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-02-17 21:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 15:50 High %user CPU in XFS Subranshu Patel
2013-02-17 21:04 ` Tru Huynh
2013-02-17 21:29 ` Dave Chinner [this message]
2013-02-17 21:25 ` Dave Chinner
2013-02-18 14:17 ` Subranshu Patel
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=20130217212932.GZ26694@dastard \
--to=david@fromorbit.com \
--cc=spatel.ml@gmail.com \
--cc=tru@pasteur.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