Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266172AbUAQTaK (ORCPT ); Sat, 17 Jan 2004 14:30:10 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266173AbUAQTaA (ORCPT ); Sat, 17 Jan 2004 14:30:00 -0500 Received: from phoenix.infradead.org ([213.86.99.234]:19983 "EHLO phoenix.infradead.org") by vger.kernel.org with ESMTP id S266170AbUAQT3y (ORCPT ); Sat, 17 Jan 2004 14:29:54 -0500 Date: Sat, 17 Jan 2004 19:29:46 +0000 From: Christoph Hellwig To: Doug Ledford Cc: Marcelo Tosatti , Arjan Van de Ven , Martin Peschke3 , Jens Axboe , Peter Yao , linux-kernel@vger.kernel.org, linux-scsi mailing list , ihno@suse.de Subject: Re: smp dead lock of io_request_lock/queue_lock patch Message-ID: <20040117192946.A6479@infradead.org> Mail-Followup-To: Christoph Hellwig , Doug Ledford , Marcelo Tosatti , Arjan Van de Ven , Martin Peschke3 , Jens Axboe , Peter Yao , linux-kernel@vger.kernel.org, linux-scsi mailing list , ihno@suse.de References: <20040112151230.GB5844@devserv.devel.redhat.com> <20040112194829.A7078@infradead.org> <1073937102.3114.300.camel@compaq.xsintricity.com> <1074345000.13198.25.camel@compaq.xsintricity.com> <20040117165828.A4977@infradead.org> <1074366452.13198.48.camel@compaq.xsintricity.com> <20040117191704.A6344@infradead.org> <1074367303.13198.52.camel@compaq.xsintricity.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <1074367303.13198.52.camel@compaq.xsintricity.com>; from dledford@redhat.com on Sat, Jan 17, 2004 at 02:21:43PM -0500 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1534 Lines: 34 On Sat, Jan 17, 2004 at 02:21:43PM -0500, Doug Ledford wrote: > I should pay more attention to what goes on in 2.6. That was a crap > decision. There are drivers out there that use global data and need one > lock across all controllers. Putting a lock in the scsi host struct for > per controller locks is a waste of space. Let the driver decide if it > needs a global driver lock, a per controller lock (in which case it > should be part of the driver private host struct), or just the global > io_request_lock. It really is up to the driver and putting it into the > scsi host struct doesn't make sense. I tend to disagree. Giving the driver control over the lock used by the midlayer is just wrong. If it has global state (which a good driver better shouldn't) it's up to the driver to protect it. That we still have a way to override that lock is the big bug rather, and in fact only three drivers are doing that, and they all override it with a lock that's per-HBA anyway. > > -- > Doug Ledford 919-754-3700 x44233 > Red Hat, Inc. > 1801 Varsity Dr. > Raleigh, NC 27606 > > ---end quoted text--- -- Christoph Hellwig - Freelance Hacker Contact me for driver hacking and kernel development consulting - 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/