All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Almateia <mike.almateia@gmail.com>
To: Gregory Farnum <gfarnum@redhat.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: NIC with Erasure offload feature support and Ceph
Date: Tue, 10 Nov 2015 11:28:14 +0300	[thread overview]
Message-ID: <5641AA9E.7050509@gmail.com> (raw)
In-Reply-To: <CAJ4mKGbA39sAek3oG9-KrvpuQcOx=9iMCojGwmE8fa_3HkLXUQ@mail.gmail.com>

03-Nov-15 18:07, Gregory Farnum пишет:
> On Tue, Nov 3, 2015 at 3:15 AM, Mike <mike.almateia@gmail.com> wrote:
>> Hello!
>>
>> In our project we planing build a petabayte cluster with Erasure pool.
>> Also we looking on Mellanox ConnectX-4 Lx EN Cards/ConnectX-4 EN Cards
>> for using its a offloading erasure code feature.
>>
>> Someone use this feature in test lab/prodaction?
>
> Nope. Ceph's erasure coding is very configurable (in terms of what
> kind of EC it's doing) but the offload features in NICs that we've
> seen aren't quite flexible enough for what Ceph is doing — it's an
> unusual use case and set of requirements where these offload cards are
> concerned. (We need to take an incoming stream, look at the raw
> stream, then erasure code it into an unknown set of pieces, and then
> send those pieces back out over the network to different addresses.)
> -Greg
>

Thanks for reply.
Mellanox said that offload Erasure Code (RedSolomon algorithm) feature 
support
on NICs will be released around April 2016.
--
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

      reply	other threads:[~2015-11-10  8:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 11:15 NIC with Erasure offload feature support and Ceph Mike
2015-11-03 15:07 ` Gregory Farnum
2015-11-10  8:28   ` Mike Almateia [this message]

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=5641AA9E.7050509@gmail.com \
    --to=mike.almateia@gmail.com \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gfarnum@redhat.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.