From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 23:06:56 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 6E20F48B for ; Wed, 2 Jul 2014 23:06:56 +0000 (UTC) Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 3E5532C77 for ; Wed, 2 Jul 2014 23:06:56 +0000 (UTC) Received: by mail-pd0-f179.google.com with SMTP id w10so12733950pde.38 for ; Wed, 02 Jul 2014 16:06:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=wJ7nRcsrMYdnSd6CwveAOtcx03Y6y7oQpWpaJ5IOa3s=; b=OwIcC7wLwds/7uFejQ/qwYkz/o77zaQDqTwIMjI3sVQvuMv5SBYZBJ1WzDwC5abLkM TdUg9cWd4FaOvk3/hzvg7QlvkT+LAVqxx3gjgouzipPbNpiOZl8Xl2DCxZzGqHnLY/n8 O3xoars8E888+RSUWMZ78T49brzI9rTbtQ4M3BO8SmKRQ4uIwRnQ5gBdmW25y7MnwUCo tzi4pnxCFeqvWCFH9ugGa8Uy6BDGqBDaMepZzJn3KXF/xO8IoTw2jMCMCTE587breFfb XGHznYHNFfQRXW/rqTM9VLup+DrnqvOYDdFwFuDgRmrxsfC8FWNu7jHw4f8HXlMLdGWm FwXg== MIME-Version: 1.0 X-Received: by 10.68.250.3 with SMTP id yy3mr926873pbc.56.1404342415887; Wed, 02 Jul 2014 16:06:55 -0700 (PDT) Sender: kob6558@gmail.com Received: by 10.66.134.4 with HTTP; Wed, 2 Jul 2014 16:06:55 -0700 (PDT) In-Reply-To: <20140702203603.GO5102@zxy.spb.ru> References: <20140626232727.GB1825@pwnie.vrt.sourcefire.com> <53ACE5B4.8070700@rice.edu> <20140701091252.GB3443@brick> <20140701231305.GA37246@zxy.spb.ru> <20140702112609.GA85758@zxy.spb.ru> <20140702203603.GO5102@zxy.spb.ru> Date: Wed, 2 Jul 2014 16:06:55 -0700 X-Google-Sender-Auth: UnvzaNVdo-PRJHNl5zFXZiQzWtk Message-ID: Subject: Re: FreeBSD iscsi target From: Kevin Oberman To: Slawa Olhovchenkov Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18 Cc: Sreenivasa Honnur , FreeBSD Current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2014 23:06:56 -0000 On Wed, Jul 2, 2014 at 1:36 PM, Slawa Olhovchenkov wrote: > On Wed, Jul 02, 2014 at 12:51:59PM -0700, Kevin Oberman wrote: > > > On Wed, Jul 2, 2014 at 4:26 AM, Slawa Olhovchenkov > wrote: > > > > > On Tue, Jul 01, 2014 at 10:43:08PM -0700, Kevin Oberman wrote: > > > > > > > On Tue, Jul 1, 2014 at 4:13 PM, Slawa Olhovchenkov > > > wrote: > > > > > > > > > On Tue, Jul 01, 2014 at 11:12:52AM +0200, Edward Tomasz Napierala > > > wrote: > > > > > > > > > > > Hi. I've replied in private, but just for the record: > > > > > > > > > > > > On 0627T0927, Sreenivasa Honnur wrote: > > > > > > > Does freebsd iscsi target supports: > > > > > > > 1. ACL (access control lists) > > > > > > > > > > > > In 10-STABLE there is a way to control access based on initiator > > > > > > name and IP address. > > > > > > > > > > > > > 2. iSNS > > > > > > > > > > > > No; it's one of the iSCSI features that seem to only be used > > > > > > for marketing purposes :-) > > > > > > > > > > > > > 3. Multiple connections per session > > > > > > > > > > > > No; see above. > > > > > > > > > > I think this is help for 40G links. > > > > > > > > > > > > > I assume that you are looking at transfer of large amounts of data > over > > > 40G > > > > links. Assuming that tis is the case, yes, multiple connections per > > > session > > > > > > Yes, this case. As I know, single transfer over 40G link limited by > > > 10G. > > > > > ??? No, not at all. Getting 40G performance over TCP is not easy, but > there > > is no 10G limitation. > > As I know (may be wrong) 40G is bundled 4x10G link. > For prevent packet reordering (when run over diferrent link) all > packets from one sessoin must be routed to same link. > Same issuse for Etherchannel. > No, 40G Ethernet is single channel from the interface perspective.. What my be confusing you is that they may use "lanes" which, for 40G, are 10.3125G. But, unlike the case with Etherchannel, these lanes are "hidden" from the MAC. The interface deals with a single stream and parcels it out over the 10G (or 25G) lanes. All 100G optical links use multiple lanes (4x25G or 10x10G), but 40G my use either a single 40G lane for distances of up to 2km or 4x10G for longer runs. Since, in most cases, 40G is used within a data center or to connect to wave gear for DWDM transmission over very long distances, most runs are under 2km, so a single 40G lane may be used. When 4 lanes are used, a ribbon cable is required to assure that all optical or copper paths are exactly the same length. Since the PMD is designed to know about and use these lanes for a single channel, the issue of packet re-ordering is not present and the protocol layers above the physical are unaware of how many lanes are used. Wikipedia has a fairly good discussion under the unfortunate title of 100 Gigabit Ethernet . Regardless of the title, the article covers both 40 and 100 Gigabit specifications as both were specified on the same standard, 802.3ba. -- R. Kevin Oberman, Network Engineer, Retired E-mail: rkoberman@gmail.com