public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Mark Fasheh <mfasheh@suse.de>
Cc: Christoph Hellwig <hch@infradead.org>,
	Jeff Mahoney <jeffm@suse.com>,
	xfs@oss.sgi.com
Subject: Re: xfs-trace-ilock-more
Date: Sun, 18 Dec 2011 15:27:34 -0500	[thread overview]
Message-ID: <20111218202734.GB20799@infradead.org> (raw)
In-Reply-To: <20111214182750.GH11114@wotan.suse.de>

On Wed, Dec 14, 2011 at 10:27:50AM -0800, Mark Fasheh wrote:
> Hey Christoph,
> 
> On Tue, Dec 13, 2011 at 09:40:40PM -0500, Christoph Hellwig wrote:
> > Can you explain the story behid this patch in SLES11SP1?
> 
> We were looking at some performance issues and needed a bit more information
> on the amount of time spent in ilock. I can give you more specifics if you
> want, I just have to dig up the e-mails (it's been a while).

Given that the patch is fairly clean can you send it to us for
inclusion?

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2011-12-18 20:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14  2:40 xfs-trace-ilock-more Christoph Hellwig
2011-12-14 18:27 ` xfs-trace-ilock-more Mark Fasheh
2011-12-14 19:24   ` xfs-trace-ilock-more Jeff Mahoney
2011-12-14 20:32     ` xfs-trace-ilock-more Dave Chinner
2011-12-14 22:42       ` xfs-trace-ilock-more Jeff Mahoney
2011-12-18 20:26     ` xfs-trace-ilock-more Christoph Hellwig
2011-12-18 20:27   ` Christoph Hellwig [this message]
2012-01-05 22:38     ` xfs-trace-ilock-more Mark Fasheh
2012-01-05 23:54       ` xfs-trace-ilock-more Dave Chinner

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=20111218202734.GB20799@infradead.org \
    --to=hch@infradead.org \
    --cc=jeffm@suse.com \
    --cc=mfasheh@suse.de \
    --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