CEPH filesystem development
 help / color / mirror / Atom feed
From: Josh Durgin <josh.durgin@inktank.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: Mark Nelson <mark.nelson@inktank.com>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: syncfs slower than without syncfs
Date: Wed, 07 Nov 2012 19:09:17 -0800	[thread overview]
Message-ID: <509B225D.2060609@inktank.com> (raw)
In-Reply-To: <509A8B98.5000707@profihost.ag>

On 11/07/2012 08:26 AM, Stefan Priebe wrote:
> Am 07.11.2012 16:04, schrieb Mark Nelson:
>> Whew, glad you found the problem Stefan!  I was starting to wonder what
>> was going on. :)  Do you mind filling a bug about the control
>> dependencies?
>
> Sure where should i fill it in?

http://www.tracker.newdream.net/projects/ceph/issues/new


  reply	other threads:[~2012-11-08  3:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-07  9:41 syncfs slower than without syncfs Stefan Priebe - Profihost AG
2012-11-07 13:31 ` Stefan Priebe - Profihost AG
2012-11-07 15:04   ` Mark Nelson
2012-11-07 16:26     ` Stefan Priebe
2012-11-08  3:09       ` Josh Durgin [this message]
2012-11-08  8:52         ` Stefan Priebe - Profihost AG

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=509B225D.2060609@inktank.com \
    --to=josh.durgin@inktank.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=mark.nelson@inktank.com \
    --cc=s.priebe@profihost.ag \
    /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