Re: FreeBSD iscsi target

From: Slawa Olhovchenkov <slw_at_zxy.spb.ru>
Date: Fri, 4 Jul 2014 14:33:15 +0400
On Fri, Jul 04, 2014 at 12:25:35PM +0200, Luigi Rizzo wrote:

> On Fri, Jul 4, 2014 at 12:16 PM, Slawa Olhovchenkov <slw_at_zxy.spb.ru> wrote:
> 
> > On Thu, Jul 03, 2014 at 08:39:42PM -0700, Kevin Oberman wrote:
> >
> > > >
> > > > In real world "Reality is quite different than it actually is".
> > > >
> > > >
> > http://www.cisco.com/c/en/us/products/collateral/switches/catalyst-6500-series-switches/white_paper_c11-696669.html
> > > >
> > > > See "Packet Path Theory of Operation. Ingress Mode".
> > > >
> > > >
> > > Yep. It is really crappy LAGG (fixed three-tupple hash... yuck!) and is
> > > really nothing but 4 10G Ethernet ports using a 40G PHY in yhe 4x10G
> > form.
> > >
> > > Note that they don't make any claim of 802.3ba compliance. It only states
> > > that "40 Gigabit Ethernet is now part of the IEEE 802.3ba standard." So
> > it
> > > is, but this device almost certainly predates the completion of the
> > > standard to get a product for which there was great demand. It's a data
> > > center product and for typical cases of large numbers of small flow, it
> > > should do the trick. Probably does not interoperate with true 80-2.3ba
> > > hardware, either.
> > >
> > > My boss at the time I retired last November was on the committee that
> > wrote
> > > 802.3ba. He would be a good authority on whether the standard has any
> > vague
> > > wording that would allow this, but he retired 5 month after I did and I
> > > have no contact information for him. But I'm pretty sure that there is no
> > > way that this is legitimate 40G Ethernet.
> >
> > 802.3ba describe only end point of ethernet.
> > ASIC, internal details of implemetations NICs, switches, fabrics --
> > out of standart scope.
> > Bottleneck can be in any point of packet flow.
> > In first pappers of netmap test demonstarated NIC can't do saturation
> > of 10G in one stream 64 bytes packet -- need use multiple rings for
> > transmit.
> >
> 
> ?that was actually just a configuration issue which since then
> has been ?resolved. The 82599 can do 14.88 Mpps on a single ring
> (and is the only 10G nic i have encountered who can do so).

Thanks for clarification.

> Besides, performance with short packets has nothing to do with the case
> you were discussing, namely throughput for a single large flow.

This is only illustration about hardware limitation.
Perforamnce may be not only bandwidth limited, but interrupt/pps (per
flow) limited.

> > I think need use general rule: one flow transfer can hit performance
> > limitation.
> >
> 
> ?This is neither a useful nor it is restricted to a single flow.
> 
> Everything "can" underperform depending
> on the hw/sw configuration, but not necessarily has to.

Yes. And estimate to ideal hw/sw configuration and enviroment -- bad
think.
Received on Fri Jul 04 2014 - 08:33:24 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:50 UTC