All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Nelson <mark.nelson@inktank.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: Sage Weil <sage@inktank.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>,
	"hch@infradead.org >> Christoph Hellwig" <hch@infradead.org>
Subject: Re: FS / Kernel question choosing the correct kernel version
Date: Tue, 26 Jun 2012 11:29:20 -0500	[thread overview]
Message-ID: <4FE9E360.8050807@inktank.com> (raw)
In-Reply-To: <4FE9E006.6030404@profihost.ag>

On 06/26/2012 11:15 AM, Stefan Priebe wrote:
> Am 26.06.2012 11:07, schrieb Stefan Priebe:
>> Am 26.06.2012 00:11, schrieb Sage Weil:
>>> On Sat, 23 Jun 2012, Stefan Priebe wrote:
>>>> Hi,
>>>>
>>>> i got stuck while selecting the right FS for ceph / RBD.
>>>>
>>>> XFS:
>>>> - deadlock / hung task under 3.0.34 in xfs_ilock / xfs_buf_lock while
>>>> syncfs
>>>
>>> There was an ilock fix that went into 3.4, IIRC. Have you tried vanilla
>>> 3.4? We are seeing some lockdep noise currently, but no deadlocks yet.
>>
>> Will test 3.4.4 soon.
>
> With btrfs i have 13-14.000 iops while doing random 4k writes from kvm.
> With XFS and 3.4.4 i have 814 ;-( and got a lot of slow request noise in
> ceph.log ;-( so 814 iops are not an option to me. Or is there anything
> special i've to respect while using XFS.
>
> Greets
> Stefan
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html

Hi Stefan,

If you can, it would be really interesting to see the blktrace results 
during these tests for both xfs and btrfs.  blktrace is in the ubuntu 
repositories and can be run quite easily from the command line during 
your test.

Thanks,
Mark


  reply	other threads:[~2012-06-26 16:29 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-23 18:26 FS / Kernel question choosing the correct kernel version Stefan Priebe
2012-06-25 22:11 ` Sage Weil
2012-06-26  8:14   ` Christoph Hellwig
2012-06-26  8:26     ` Stefan Priebe
2012-06-26  9:39     ` Stefan Priebe
2012-06-26 16:02     ` Sage Weil
2012-06-26  9:07   ` Stefan Priebe
2012-06-26 16:15     ` Stefan Priebe
2012-06-26 16:29       ` Mark Nelson [this message]
2012-06-26 16:43         ` Stefan Priebe
2012-06-26 16:59           ` Mark Nelson
2012-06-26 17:49             ` Stefan Priebe
2012-06-26 17:49               ` Stefan Priebe
2012-06-26 18:04                 ` Stefan Priebe
2012-06-26 20:07                   ` Mark Nelson

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=4FE9E360.8050807@inktank.com \
    --to=mark.nelson@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=hch@infradead.org \
    --cc=s.priebe@profihost.ag \
    --cc=sage@inktank.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.