All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Priebe <s.priebe@profihost.ag>
To: "Atchley, Scott" <atchleyes@ornl.gov>
Cc: Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com>,
	Mark Nelson <mark.nelson@inktank.com>,
	Joseph Glanville <joseph.glanville@orionvm.com.au>,
	Sage Weil <sage@inktank.com>,
	"ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: flashcache
Date: Thu, 17 Jan 2013 17:20:24 +0100	[thread overview]
Message-ID: <50F824C8.3040704@profihost.ag> (raw)
In-Reply-To: <D36B9470-CEF7-43D2-83E3-F91ABA983100@ornl.gov>

Hi,

Am 17.01.2013 17:12, schrieb Atchley, Scott:
> On Jan 17, 2013, at 11:01 AM, Gandalf Corvotempesta <gandalf.corvotempesta@gmail.com> wrote:
>
>> 2013/1/17 Atchley, Scott <atchleyes@ornl.gov>:
>>> Yes. It should get close to 1 GB/s where 1GbE is limited to about 125 MB/s. Lower latency? Probably since most Ethernet drivers set interrupt coalescing by default. Intel e1000 driver, for example, have a cluster mode that reduces (or turns off) interrupt coalescing. I don't know if ceph is latency sensitive or not.
>>
>> Sorry, I meant 10GbE.
>
> 10GbE should get close to 1.2 GB/s compared to 1 GB/s for IB SDR. Latency again depends on the Ethernet driver.

We're using bonded active/active 2x10GbE with Intel ixgbe and i'm able 
to get 2.3GB/s.

Not sure how to measure latency effectively.

Stefan

  parent reply	other threads:[~2013-01-17 16:20 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-16 21:22 flashcache Gandalf Corvotempesta
2013-01-16 21:29 ` flashcache Sage Weil
2013-01-16 21:42   ` flashcache Gandalf Corvotempesta
2013-01-16 21:46     ` flashcache Sage Weil
2013-01-16 21:55       ` flashcache Mark Nelson
2013-01-16 21:59         ` flashcache Gandalf Corvotempesta
2013-01-16 21:57       ` flashcache Gandalf Corvotempesta
2013-01-16 21:53   ` flashcache Mark Nelson
2013-01-16 22:04     ` flashcache Gandalf Corvotempesta
2013-01-17  5:47     ` flashcache Stefan Priebe - Profihost AG
2013-01-17 13:34       ` flashcache Mark Nelson
2013-01-17  9:46     ` flashcache Gandalf Corvotempesta
2013-01-17 13:32       ` flashcache Joseph Glanville
2013-01-17 13:37         ` flashcache Mark Nelson
2013-01-17 13:44           ` flashcache Gandalf Corvotempesta
2013-01-17 14:30           ` flashcache Atchley, Scott
2013-01-17 14:48             ` flashcache Gandalf Corvotempesta
2013-01-17 15:00               ` flashcache Atchley, Scott
2013-01-17 15:07                 ` flashcache Andrey Korolyov
2013-01-17 15:47                   ` flashcache Atchley, Scott
2013-01-17 16:39                     ` flashcache Andrey Korolyov
2013-01-20  2:56                       ` flashcache Joseph Glanville
2013-01-21 23:57                         ` flashcache John Nielsen
2013-01-30 20:10                           ` flashcache Joseph Glanville
2013-01-17 15:14                 ` flashcache Gandalf Corvotempesta
2013-01-17 15:50                   ` flashcache Atchley, Scott
2013-01-17 16:01                     ` flashcache Gandalf Corvotempesta
2013-01-17 16:12                       ` flashcache Atchley, Scott
2013-01-17 16:19                         ` flashcache Gandalf Corvotempesta
2013-01-22 21:06                           ` flashcache Atchley, Scott
2013-01-22 21:08                             ` flashcache Atchley, Scott
2013-01-17 16:20                         ` Stefan Priebe [this message]
2013-01-17 16:21                           ` flashcache Gandalf Corvotempesta
2013-01-17 16:24                             ` flashcache Stefan Priebe

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=50F824C8.3040704@profihost.ag \
    --to=s.priebe@profihost.ag \
    --cc=atchleyes@ornl.gov \
    --cc=ceph-devel@vger.kernel.org \
    --cc=gandalf.corvotempesta@gmail.com \
    --cc=joseph.glanville@orionvm.com.au \
    --cc=mark.nelson@inktank.com \
    --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.