All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Benjamin <mbenjami@redhat.com>
To: Josh Durgin <jdurgin@redhat.com>
Cc: Sage Weil <sweil@redhat.com>, Gregory Farnum <gfarnum@redhat.com>,
	Xie Xingguo <xie.xingguo@zte.com.cn>,
	ceph-devel <ceph-devel@vger.kernel.org>
Subject: Re: Why does Erasure-pool not support omap?
Date: Thu, 26 Oct 2017 13:32:41 -0400	[thread overview]
Message-ID: <CAKOnarnmiDeQxWJLRZ7GJc-xdTzxsR-5=AiUxKTUte0h9XxLoQ@mail.gmail.com> (raw)
In-Reply-To: <1e168a03-ec8f-36c9-f444-550738f4c0f1@redhat.com>

On Thu, Oct 26, 2017 at 12:21 PM, Josh Durgin <jdurgin@redhat.com> wrote:
> On 10/26/2017 07:26 AM, Sage Weil wrote:
>>

>
> If this is only for rbd, we might as well store k+m copies since there's
> so little omap data.
>
> I agree cephfs and rgw continue to refuse to use EC for metadata, since
> their omap use gets far to large and is in the data path.

This highlights, but isn't an answer to the problem.  What RGW
actually has is a split data path, when data is on EC.

Matt

-- 

Matt Benjamin
Red Hat, Inc.
315 West Huron Street, Suite 140A
Ann Arbor, Michigan 48103

http://www.redhat.com/en/technologies/storage

tel.  734-821-5101
fax.  734-769-8938
cel.  734-216-5309

  reply	other threads:[~2017-10-26 17:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201710251652060421729@zte.com.cn>
2017-10-25 12:16 ` Why does Erasure-pool not support omap? Sage Weil
2017-10-25 18:57   ` Josh Durgin
2017-10-26 14:20     ` Gregory Farnum
2017-10-26 14:26       ` Sage Weil
2017-10-26 15:07         ` Matt Benjamin
2017-10-26 15:08         ` Jason Dillaman
2017-10-26 15:35           ` Matt Benjamin
2017-10-26 15:49             ` Jason Dillaman
2017-10-26 15:50               ` Matt Benjamin
2017-10-26 16:10           ` Sage Weil
2017-10-26 16:21         ` Josh Durgin
2017-10-26 17:32           ` Matt Benjamin [this message]
2017-10-30 22:48           ` Gregory Farnum
2017-10-31  2:26             ` Sage Weil
2017-11-01 20:27               ` Gregory Farnum

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='CAKOnarnmiDeQxWJLRZ7GJc-xdTzxsR-5=AiUxKTUte0h9XxLoQ@mail.gmail.com' \
    --to=mbenjami@redhat.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gfarnum@redhat.com \
    --cc=jdurgin@redhat.com \
    --cc=sweil@redhat.com \
    --cc=xie.xingguo@zte.com.cn \
    /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.