Re: [storm] Removing iSCSI Markers?

"Mark Bakke (mbakke)" <mbakke@cisco.com> Fri, 02 April 2010 21:38 UTC

Return-Path: <mbakke@cisco.com>
X-Original-To: storm@core3.amsl.com
Delivered-To: storm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9BF423A6925 for <storm@core3.amsl.com>; Fri, 2 Apr 2010 14:38:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.219
X-Spam-Level:
X-Spam-Status: No, score=-6.219 tagged_above=-999 required=5 tests=[AWL=0.650, BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 64UqaL6liDaj for <storm@core3.amsl.com>; Fri, 2 Apr 2010 14:38:52 -0700 (PDT)
Received: from rtp-iport-2.cisco.com (rtp-iport-2.cisco.com [64.102.122.149]) by core3.amsl.com (Postfix) with ESMTP id B6C983A6AF4 for <storm@ietf.org>; Fri, 2 Apr 2010 14:26:29 -0700 (PDT)
Authentication-Results: rtp-iport-2.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Ai0FAD7+tUutJV2Y/2dsb2JhbACBPY1njClxmx+YXIJoBwGCFQSDJA
X-IronPort-AV: E=Sophos; i="4.51,355,1267401600"; d="scan'208,217"; a="98520961"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by rtp-iport-2.cisco.com with ESMTP; 02 Apr 2010 21:27:03 +0000
Received: from xbh-rcd-202.cisco.com (xbh-rcd-202.cisco.com [72.163.62.201]) by rcdn-core-1.cisco.com (8.14.3/8.14.3) with ESMTP id o32LR2g6000921; Fri, 2 Apr 2010 21:27:02 GMT
Received: from xmb-rcd-105.cisco.com ([72.163.62.147]) by xbh-rcd-202.cisco.com with Microsoft SMTPSVC(6.0.3790.3959); Fri, 2 Apr 2010 16:27:02 -0500
X-MimeOLE: Produced By Microsoft Exchange V6.5
x-cr-hashedpuzzle: Bpca DTNg E7O7 HGB3 HhtQ HlNX LZo3 MTVK NanI Ofcy PQPU RFPN RQvu T0sK UKjE aCAB; 3; bQBhAHIAawBlAEAAbQB1AHQAdABzAG4AdQB0AHMALgBjAG8AbQA7AHAAdABoAGEAbABlAHIAQABiAHIAbwBhAGQAYwBvAG0ALgBjAG8AbQA7AHMAdABvAHIAbQBAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {97AE992C-C4E9-4AC0-9D6B-D2601AFE0929}; bQBiAGEAawBrAGUAQABjAGkAcwBjAG8ALgBjAG8AbQA=; Fri, 02 Apr 2010 21:26:52 GMT; UgBFADoAIABbAHMAdABvAHIAbQBdACAAUgBlAG0AbwB2AGkAbgBnACAAaQBTAEMAUwBJACAATQBhAHIAawBlAHIAcwA/AA==
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01CAD2AB.3BFF7426"
x-cr-puzzleid: {97AE992C-C4E9-4AC0-9D6B-D2601AFE0929}
Content-class: urn:content-classes:message
Date: Fri, 2 Apr 2010 16:26:52 -0500
Message-ID: <97CC2D4896BE5D48825529CE9A168825013B0745@XMB-RCD-105.cisco.com>
In-Reply-To: <DBFBCB90599B2C46992032279293D10010D62A9CBE@SJEXCHCCR01.corp.ad.broadcom.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [storm] Removing iSCSI Markers?
Thread-Index: AcrQJUCnv+W4g5cTTFKOkIPGk8wCzACZO8XwAAgzGyA=
References: <C2D311A6F086424F99E385949ECFEBCB02162B4B@CORPUSMX80B.corp.emc.com><690958.35528.qm@smtp111.biz.mail.re2.yahoo.com><SNT131-ds389E5D120CA34D81D341FA01F0@phx.gbl><D8CEBB6AE9D43848BD2220619A43F326539198@M31.equallogic.com><SNT129-W39116021288D2177842E5DE61F0@phx.gbl><D8CEBB6AE9D43848BD2220619A43F3265391BE@M31.equallogic.com><288331.47396.qm@smtp113.biz.mail.re2.yahoo.com><SNT129-W518EAD0118AE20545198F3E61F0@phx.gbl><719511.28420.qm@smtp115.biz.mail.re2.yahoo.com> <DBFBCB90599B2C46992032279293D10010D62A9CBE@SJEXCHCCR01.corp.ad.broadcom.com>
From: "Mark Bakke (mbakke)" <mbakke@cisco.com>
To: "Pat Thaler" <pthaler@broadcom.com>, "Mark S. Edwards" <marke@muttsnuts.com>, <storm@ietf.org>
X-OriginalArrivalTime: 02 Apr 2010 21:27:02.0373 (UTC) FILETIME=[3C244150:01CAD2AB]
Subject: Re: [storm] Removing iSCSI Markers?
X-BeenThere: storm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Storage Maintenance WG <storm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/storm>
List-Post: <mailto:storm@ietf.org>
List-Help: <mailto:storm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/storm>, <mailto:storm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Apr 2010 21:38:54 -0000

Cisco doesn't use markers, either, and has no plans to do so.  I agree
that with the RDMA/iSER work that could be used similar purposes,
there's no need for them in the iSCSI protocol.

 

Mark

 

From: storm-bounces@ietf.org [mailto:storm-bounces@ietf.org] On Behalf
Of Pat Thaler
Sent: Friday, April 02, 2010 12:39 PM
To: Mark S. Edwards; storm@ietf.org
Subject: Re: [storm] Removing iSCSI Markers?

 

We also don't use markers.

 

I don't recall Randy's presentation, but markers only partially allow
out of order placement. If you didn't receive the header of the PDU, you
can't place. By the time you take that into account plus the cost of
implementing markers, they aren't worth whatever memory savings they
might allow. And for various reasons, a 10G offload NIC needs a lot more
than 2K RAM.

 

Regards,

Pat

 

________________________________

From: storm-bounces@ietf.org [mailto:storm-bounces@ietf.org] On Behalf
Of Mark S. Edwards
Sent: Tuesday, March 30, 2010 9:22 AM
To: storm@ietf.org
Subject: Re: [storm] Removing iSCSI Markers?

Asgeir,

Yes, I do understand and remember all the arguments.  Indeed, I remember
one of Randy's theoretical presentations positing that a marker aware
10GB offload NIC might only require as little as 2K onboard buffering
RAM.

The point is, that at least for iSCSI the technology that arrived seems
to marginalised the need for anyone to implement markers.  Given the
fact that running code creates IETF consensus we have an opportunity at
this time to remove unnecessary complications, markers are a candidate
for being made optional or even being removed completely.

Personally I would be happy to see them removed.  My original note on
this topic was to try to be a good citizen by asking anyone who might be
affected, or know someone who would be affected, to speak up.

Mark.


At 16:28 30/03/2010, Asgeir Eiriksson wrote:



Paul, Mark
 
The main selling point for markers is that they enable out or order
placement
(on receive) while preserving in order completions and markers therefore
have the
potential of decreasing buffering requirements in RNIC and to a less
extent in
iSCSI HBA.
 
'Asgeir 
 

________________________________

Date: Tue, 30 Mar 2010 15:49:11 +0100
To: storm@ietf.org
From: marke@muttsnuts.com
Subject: Re: [storm] Removing iSCSI Markers?

Paul,

That's pretty much my recollection, too.

One of those things that was thought to be a reasonable solution to a
foreseeable change in the technology.  In the end, the technology found
a different solution.

They were fascinating presentations, though.

Mark.

At 15:22 30/03/2010, Paul Koning wrote:

Thanks Asgeir.


  

As I recall, the original idea behind markers is to make it possible to
build 10G HBAs that can run at wire speed, which was believed to be
impossible otherwise.


  

The subsequent record indicates that this was in fact not the case; 10G
HBAs are feasible and have been built without resorting to markers.
There is no other reason for using markers.  So if the one reason that
they were thought to be needed in fact turned out not to be real, the
obvious thing to do is to remove the unused complications from the spec.


  

I suppose one could argue that, placed in an appendix and optional to
implement they do no harm.  Thats a fair point.  If there is still a
chance that they will turn out to be needed in the future we may want to
go that way.  I personally would bet against that chance.


  

                paul 


  

From: Asgeir Eiriksson [ mailto:asgeir_eiriksson@hotmail.com] 

Sent: Tuesday, March 30, 2010 9:24 AM

To: Paul Koning; cbm@chadalapaka.com; marke@muttsnuts.com;
storm@ietf.org

Subject: RE: [storm] Removing iSCSI Markers?


  

Hello Paul,


  

The Chelsio RNIC do support the marker feature, but as far as I know the
feature

has never been used in the field, and it isn't supported by all RNIC

implementations. 


  

I periodically ask our AE and developers about this feature and so far
the answer

is that no one uses it, and no one is asking for it (4 years of data at
this point).


  

Regards,


  

Asgeir Eiriksson

CTO

Chelsio Communications Inc.


  

> Date: Mon, 29 Mar 2010 21:01:49 -0400

> From: Paul_Koning@Dell.com

> To: cbm@chadalapaka.com; marke@muttsnuts.com; storm@ietf.org

> Subject: Re: [storm] Removing iSCSI Markers?

> 

> I sure would like markers to go away. Rumors of their use are somewhat

> interesting, but substantiated data would be more so.

> 

> paul

> 

> > -----Original Message-----

> > From: storm-bounces@ietf.org [ mailto:storm-bounces@ietf.org] On
Behalf

> > Of Mallikarjun Chadalapaka

> > Sent: Monday, March 29, 2010 8:33 PM

> > To: 'Mark S. Edwards'; storm@ietf.org

> > Subject: [storm] Removing iSCSI Markers?

> > 

> > Just to clarify...

> > 

> > > On another removal topic, I seem to recall that Mallikarjun also

> said

> > > that he was removing markers.

> > 

> > I had only said that it's one of the items I had heard prior
requests

> > on

> > (that it be removed). Thanks for initiating the list discussion

> > though!

> > 

> > > but I do wonder if this will affect any HBA implementations ?

> > 

> > Good question, I don't know. HBA vendors, especially iSCSI/iSER/RNIC

> > "roto-tilled" implementations, please chime in.

> > 

> > 

> > Mallikarjun

> > 

> > 

> > 

> > > -----Original Message-----

> > > From: storm-bounces@ietf.org [ mailto:storm-bounces@ietf.org] On

> > Behalf Of

> > Mark

> > > S. Edwards

> > > Sent: Saturday, March 27, 2010 6:56 AM

> > > To: storm@ietf.org

> > > Subject: Re: [storm] Draft minutes from Anaheim

> > >

> > > Regarding the feature removal discussion, can I add SLP to the
list

> ?

> > >

> > > The RFC 3721 states

> > >

> > > "iSCSI equipment that

> > > need discovery functions beyond SendTargets should at least

> > > implement SLP, and then consider iSNS when extended discovery

> > > management capabilities are required such as in larger

> storage

> > > networks. It should be noted that since iSNS will support

> > SLP,

> > > iSNS can be used to help manage the discovery information

> > returned

> > > by SLP."

> > >

> > > The implication is that targets and initiators should expect to
find

> > > support for SLP before considering iSNS.

> > >

> > > I remember our first iSCSI appliance and we spent ages trying to
get

> > > SLP working because it the above wording effectively made it

> > > mandatory. SLP turned out to be a complete bust and was
effectively

> > > killed off when Microsoft refused to support it in their initiator

> > > and in their target logo tests.

> > >

> > > The result is that today I doubt you could find a target or

> initiator

> > > out there supporting SLP.

> > >

> > > For anybody that does still implement SLP we could change the

> wording

> > > for SLP a little to remove the implied hierarchy, or just admit
that

> > > running code has created IETF consensus.

> > >

> > >

> > > On another removal topic, I seem to recall that Mallikarjun also

> said

> > > that he was removing markers. I don't particularly object to this

> > > but I do wonder if this will affect any HBA implementations ?

> > >

> > > Regards,

> > >

> > > Mark.

> > >

> > >

> > > At 06:59 27/03/2010, Black_David@emc.com wrote:

> > > >Draft minutes are attached - please comment, correct, etc.

> > > >

> > > >Also, in the absence of objection on this mailing list, decisions

> > > >recorded in the minutes are considered to be the rough consensus
of

> > > >this WG, *except* that two issues were identified as sufficiently

> > > >important to discuss separately on the list (see separate

> messages):

> > > > - Text negotiation key for new iSCSI features (discussion

> > > > in progress)

> > > > - Features to remove from iSCSI (discussion to be started)

> > > >

> > > >Many thanks to Craig Carlson for taking notes during the meeting.

> > > >

> > > >Thanks,

> > > >--David

> > > >----------------------------------------------------

> > > >David L. Black, Distinguished Engineer

> > > >EMC Corporation, 176 South St., Hopkinton, MA 01748

> > > >+1 (508) 293-7953 FAX: +1 (508) 293-7786

> > > >black_david@emc.com Mobile: +1 (978) 394-7754

> > > >----------------------------------------------------

> > > >

> > > >

> > > >

> > > >

> > > >_______________________________________________

> > > >storm mailing list

> > > >storm@ietf.org

> > > > https://www.ietf.org/mailman/listinfo/storm

> > >

> > > _______________________________________________

> > > storm mailing list

> > > storm@ietf.org

> > > https://www.ietf.org/mailman/listinfo/storm

> > 

> > _______________________________________________

> > storm mailing list

> > storm@ietf.org

> > https://www.ietf.org/mailman/listinfo/storm

> _______________________________________________

> storm mailing list

> storm@ietf.org

> https://www.ietf.org/mailman/listinfo/storm

________________________________

Hotmail is redefining busy with tools for the New Busy. Get more from
your inbox. Sign up now.
<http://www.windowslive.com/campaign/thenewbusy?ocid=PID27925::T:WLMTAGL
:ON:WL:en-US:WM_HMP:032010_2> 

 

________________________________

Hotmail has tools for the New Busy. Search, chat and e-mail from your
inbox. Learn More.
<http://www.windowslive.com/campaign/thenewbusy?ocid=PID27925::T:WLMTAGL
:ON:WL:en-US:WM_HMP:032010_1>