From owner-freebsd-hackers@FreeBSD.ORG Wed Jul 2 16:37:45 2014 Return-Path: Delivered-To: freebsd-hackers@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 D0874D08; Wed, 2 Jul 2014 16:37:45 +0000 (UTC) Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) (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 98D1D284C; Wed, 2 Jul 2014 16:37:45 +0000 (UTC) Received: by mail-pa0-f47.google.com with SMTP id kq14so12800514pab.34 for ; Wed, 02 Jul 2014 09:37:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=UbNdGKoyMkUYJ/tQAnY1U7W0+OuScCGqPo9W+1doh6g=; b=WVAzbqfqhbEIz2Cw9cdIr/fUnDXiyObI23gNAFcbcXZ1GS/9nRMtt2+woFiMCR+ZLs yCHsxSeoGfVZTh2jpVdTnBGRQ7GcLMdMVfl9zvQmENmquBMzMoij8C7v+enaVS1K7/1s ieHjaMPqLDoJT8UP+kcNe3+PKK1ackxoSXzKNbj6+H+eikm/TTSlZQ91pO7WjYEaZQZe gYNomBhjQihhRV+mkjtckbJEEYT2chSmKfXx/hsZPvl1lLwr5ASlp/yOmmonAtRAf/q5 OJS+E4ObHhz2MIq3TTu9tHMA9xxjcFcQQrWWj3kjpy2qIXOIjLF8YjTGENLQrNpqPKTe osiA== X-Received: by 10.70.61.4 with SMTP id l4mr1240620pdr.112.1404319065163; Wed, 02 Jul 2014 09:37:45 -0700 (PDT) Received: from ox ([24.6.44.228]) by mx.google.com with ESMTPSA id fz3sm2203803pdb.78.2014.07.02.09.37.43 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Wed, 02 Jul 2014 09:37:44 -0700 (PDT) Date: Wed, 2 Jul 2014 09:37:39 -0700 From: Navdeep Parhar To: Slawa Olhovchenkov Subject: Re: FreeBSD iscsi target Message-ID: <20140702163739.GA3957@ox> Mail-Followup-To: Slawa Olhovchenkov , Kevin Oberman , "freebsd-hackers@freebsd.org" , Sreenivasa Honnur , FreeBSD Current References: <20140626232727.GB1825@pwnie.vrt.sourcefire.com> <53ACE5B4.8070700@rice.edu> <20140701091252.GB3443@brick> <20140701231305.GA37246@zxy.spb.ru> <20140702112609.GA85758@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140702112609.GA85758@zxy.spb.ru> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Kevin Oberman , Sreenivasa Honnur , FreeBSD Current , "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 02 Jul 2014 16:37:46 -0000 On Wed, Jul 02, 2014 at 03:26:09PM +0400, 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. This is not correct. A 40Gb link does not limit a single transfer to 10G. For example, on FreeBSD all common bandwidth benchmarks reach 40GbE line rate with a single TCP connection at mtu 1500. If a single transfer were limited to 10G you'd need 4 connections to get there. The physical signalling is over four lanes so it's easy to split a 40G link into four separate 10G links. But when running as a 40GbE (this is the usual case) the hardware will combine all the lanes into a single 40G data stream, and you get to use all of the bandwidth. Regards, Navdeep