From owner-freebsd-current@FreeBSD.ORG Wed Jul 2 11:26:14 2014 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BDCB158F; Wed, 2 Jul 2014 11:26:14 +0000 (UTC) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 75F0C2984; Wed, 2 Jul 2014 11:26:14 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1X2Ifx-000Dvg-T8; Wed, 02 Jul 2014 15:26:09 +0400 Date: Wed, 2 Jul 2014 15:26:09 +0400 From: Slawa Olhovchenkov To: Kevin Oberman Subject: Re: FreeBSD iscsi target Message-ID: <20140702112609.GA85758@zxy.spb.ru> References: <20140626232727.GB1825@pwnie.vrt.sourcefire.com> <53ACE5B4.8070700@rice.edu> <20140701091252.GB3443@brick> <20140701231305.GA37246@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: "freebsd-hackers@freebsd.org" , 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 11:26:14 -0000 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.