Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965097AbVINRN0 (ORCPT ); Wed, 14 Sep 2005 13:13:26 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965247AbVINRNZ (ORCPT ); Wed, 14 Sep 2005 13:13:25 -0400 Received: from e35.co.us.ibm.com ([32.97.110.133]:49105 "EHLO e35.co.us.ibm.com") by vger.kernel.org with ESMTP id S965097AbVINRNY (ORCPT ); Wed, 14 Sep 2005 13:13:24 -0400 Date: Wed, 14 Sep 2005 10:13:07 -0700 From: Patrick Mansfield To: Luben Tuikov Cc: Douglas Gilbert , James Bottomley , ltuikov@yahoo.com, Linux Kernel Mailing List , SCSI Mailing List Subject: Re: [PATCH 2.6.13 5/14] sas-class: sas_discover.c Discover process (end devices) Message-ID: <20050914171307.GA10044@us.ibm.com> References: <20050910024454.20602.qmail@web51613.mail.yahoo.com> <1126368081.4813.46.camel@mulgrave> <4325997D.3050103@adaptec.com> <20050912162739.GA11455@us.ibm.com> <4326964B.9010503@torque.net> <20050913224215.GB1308@us.ibm.com> <4328176D.80307@adaptec.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4328176D.80307@adaptec.com> User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1548 Lines: 47 On Wed, Sep 14, 2005 at 08:28:29AM -0400, Luben Tuikov wrote: > On 09/13/05 18:42, Patrick Mansfield wrote: > > What I mean is that the target has to intercept the command whether it is > > a REPORT LUN or for the well known (W_LUN). > > > > The target (firmware) code has to have code today like: > > > > if (cmd == REPORT_LUN) { > > do_report_lun(); > > } > > > > For only W_LUN support, the code might be something like: > > > > if (lun == W_LUN) { > > if (cmd == REPORT_LUN) { > > do_report_lun(); > > } > > } > > > > But the first case above already covers even the W_LUN case. > > _Except_, that what the firmware actually does is, it routes > the tasks by LUN first, _before_ looking up with what the command > is.* This is crucial. That is what the second code snippet above is meant to show. > > So adding a W_LUN at this point does not add any value ... maybe it looks > > nice in the spec and in someones firmware, but it does not add anything > > that I can see. > > I wonder if the maintainer of the SCSI Core would listen or ignore your > opinion here. > I wonder _who_ decides here where speculation ends and industry > opinion starts? I am talking about the scsi spec, not the code. IMO linux scsi code should support W_LUN and 64 bit LUN. -- Patrick Mansfield - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/