Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1762163AbZDQRng (ORCPT ); Fri, 17 Apr 2009 13:43:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761017AbZDQRnF (ORCPT ); Fri, 17 Apr 2009 13:43:05 -0400 Received: from moutng.kundenserver.de ([212.227.126.177]:60376 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758709AbZDQRnD (ORCPT ); Fri, 17 Apr 2009 13:43:03 -0400 Message-ID: <49E8BFB2.50608@vlnb.net> Date: Fri, 17 Apr 2009 21:43:14 +0400 From: Vladislav Bolkhovitin User-Agent: Thunderbird 2.0.0.21 (X11/20090320) MIME-Version: 1.0 To: James Smart CC: Daniel Debonzi , "scst-devel@lists.sourceforge.net" , "linux-kernel@vger.kernel.org" , "linux-scsi@vger.kernel.org" Subject: Re: [Scst-devel] Discussion about SCST sysfs layout and implementation. References: <49E7307A.8000205@vlnb.net> <49E77795.7080204@linux.vnet.ibm.com> <49E85F1C.7040106@vlnb.net> <49E8832F.6070302@linux.vnet.ibm.com> <49E88E3F.8030107@vlnb.net> <49E891C8.1050007@emulex.com> In-Reply-To: <49E891C8.1050007@emulex.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX1+J5KgxTsU5tU5b6oXLb7fIY/nWHnkdQCcPPt2 q8Rx9/NfdorANT551yUl0EvjIe4mE8pdztzCc3wTc1RfePAXGM n1s97eKZzX3ojtV0Xzfvw== Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1289 Lines: 29 James Smart, on 04/17/2009 06:27 PM wrote: > Vladislav Bolkhovitin wrote: >> Let's go with root in /sys/class/scsi_tgt. In future, if somebody >> objects, we can easily change it. > > This maps too closely to the scsi midlayer names, especially the real > target devices initiators see - which are not yet in sysfs but there has > been discussion of in the past. I would prefer that you used > /sys/class/scst_tgt. And yes, as part of the class level support in the > midlayer/kernel, they are generally symlinks to the actual kobject in > the /sys/devices that the class entity corresponds to. > > IMHO - "scsi_tgt" also seems a bit presumptuous to propose if SCST is > not, in it's entirety, going to be the adapter target interface pulled > in upstream. Thus, another reason I prefer the "scst_tgt" name, as it > makes it very specific to SCST itself, and lessens any co-existence > conflicts if there are any in the future. James, Thank you for the suggestion. If nobody objects, we will go with /sys/class/scst_tgt. Vlad -- 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/