Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758117AbYAGRVc (ORCPT ); Mon, 7 Jan 2008 12:21:32 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755633AbYAGRVU (ORCPT ); Mon, 7 Jan 2008 12:21:20 -0500 Received: from ns2.suse.de ([195.135.220.15]:52160 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751489AbYAGRVT (ORCPT ); Mon, 7 Jan 2008 12:21:19 -0500 Date: Mon, 7 Jan 2008 09:20:09 -0800 From: Greg KH To: Stefan Richter Cc: James.Bottomley@hansenpartnership.com, dbrownell@users.sourceforge.net, Dave Young , linux-scsi@vger.kernel.org, a.zummo@towertech.it, peterz@infradead.org, cbou@mail.ru, linux-kernel@vger.kernel.org, David Brownell , krh@redhat.com, stern@rowland.harvard.edu, rtc-linux@googlegroups.com, spi-devel-general@lists.sourceforge.net, linux1394-devel@lists.sourceforge.net, dwmw2@infradead.org, davem@davemloft.net, jarkao2@gmail.com Subject: Re: [PATCH 0/7] convert semaphore to mutex in struct class Message-ID: <20080107172009.GA25943@suse.de> References: <20080103055019.GA4885@darkstar.te-china.tietoenator.com> <20080107020944.GA3637@darkstar.te-china.tietoenator.com> <20080107084528.GA8365@suse.de> <200801070101.15168.david-b@pacbell.net> <478227D5.8050402@s5r6.in-berlin.de> <20080107154404.GA10880@suse.de> <47825DC1.3090102@s5r6.in-berlin.de> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <47825DC1.3090102@s5r6.in-berlin.de> User-Agent: Mutt/1.5.16 (2007-06-09) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1178 Lines: 27 On Mon, Jan 07, 2008 at 06:13:37PM +0100, Stefan Richter wrote: > It's already in the driver core to the most part. It remains to be seen > what is less complicated in the end: Transparent mutex-protected list > accesses provided by driver core (requires the iterator), or all the > necessary locking done by the drivers themselves (requires some more > lock-taking but perhaps fewer lock instances overall in the drivers, and > respective redefinitions and documentation of the driver core API). I favor changing the driver core api and doing this kind of thing there. It keeps the drivers simpler and should hopefully make their lives easier. > Semi off-topic: What about struct device.sem? Is there any chance to > rip this out of the driver core and let drivers serialize everything? I > suppose not... See the previous long threads about this very topic, that is what caused this class.sem patches :) thanks, greg k-h -- 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/