From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030424AbWGUBGg (ORCPT ); Thu, 20 Jul 2006 21:06:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030423AbWGUBGg (ORCPT ); Thu, 20 Jul 2006 21:06:36 -0400 Received: from ns.virtualhost.dk ([195.184.98.160]:5717 "EHLO virtualhost.dk") by vger.kernel.org with ESMTP id S1030425AbWGUBGf (ORCPT ); Thu, 20 Jul 2006 21:06:35 -0400 Date: Fri, 21 Jul 2006 03:06:22 +0200 From: Jens Axboe To: Jeff Garzik Cc: Ed Lin , "linux-scsi@vger.kernel.org" , "James.Bottomley" , hch , linux-kernel , akpm , promise_linux Subject: Re: [PATCH] Promise 'stex' driver Message-ID: <20060721010622.GA24176@suse.de> References: <44BFF539.4000700@garzik.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <44BFF539.4000700@garzik.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 20 2006, Jeff Garzik wrote: > 5) [agreement/correction] The block tagging API supports adapter-wide > tags just fine. HOWEVER, I nonetheless feel that block tagging API use > should be considered post-merge. The 'stex' driver is working and > tested today. Since _no individual SCSI driver_ uses the block layer > tagging, it is likely that some instability and core kernel development > will occur, in order to make that work. I'd disagree. If the driver gets merged with the current tagging, I'll get you two beers that it never gets changed. And you are wrong, block layer tagging is used by at least one SCSI driver. We definitely need to start pushing it more. -- Jens Axboe