Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753418AbcCRWfY (ORCPT ); Fri, 18 Mar 2016 18:35:24 -0400 Received: from smtprelay0167.hostedemail.com ([216.40.44.167]:53281 "EHLO smtprelay.hostedemail.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1751350AbcCRWfW (ORCPT ); Fri, 18 Mar 2016 18:35:22 -0400 X-Session-Marker: 6A6F6540706572636865732E636F6D X-Spam-Summary: 2,0,0,,d41d8cd98f00b204,joe@perches.com,:::::::,RULES_HIT:41:355:379:541:599:800:960:973:988:989:1260:1277:1311:1313:1314:1345:1359:1373:1437:1515:1516:1518:1534:1540:1593:1594:1711:1730:1747:1777:1792:2393:2559:2562:2828:3138:3139:3140:3141:3142:3352:3622:3865:3866:3867:3868:3870:3871:3872:3874:4321:5007:6261:7576:10004:10400:10848:11026:11232:11658:11914:12517:12519:12740:13069:13311:13357:13439:14659:14721:21080:30054:30070:30091,0,RBL:none,CacheIP:none,Bayesian:0.5,0.5,0.5,Netcheck:none,DomainCache:0,MSF:not bulk,SPF:fn,MSBL:0,DNSBL:none,Custom_rules:0:0:0,LFtime:2,LUA_SUMMARY:none X-HE-Tag: balls28_4baef7c52b541 X-Filterd-Recvd-Size: 1730 Message-ID: <1458340518.26915.30.camel@perches.com> Subject: Re: [PATCH] net: consolidate lock/unlock into unlock_wait From: Joe Perches To: David Miller , hofrat@osadl.org Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org Date: Fri, 18 Mar 2016 15:35:18 -0700 In-Reply-To: <20160318.173702.788700055531273267.davem@davemloft.net> References: <1458293525-16842-1-git-send-email-hofrat@osadl.org> <20160318.173702.788700055531273267.davem@davemloft.net> Content-Type: text/plain; charset="ISO-8859-1" X-Mailer: Evolution 3.18.5.1-1ubuntu1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 825 Lines: 24 On Fri, 2016-03-18 at 17:37 -0400, David Miller wrote: > From: Nicholas Mc Guire > > The spin_lock()/spin_unlock() is synchronizing on the adapter->work_lock > > as the comment also suggests, which is equivalent to spin_unlock_wait() > > but the later should be more efficient. [] > There really is no justification for this change. > This is an optimization in a slow-path of the driver. > The device is a rarely used older piece of hardware. It really might be nice to take some of the ancient hardware drivers in drivers/net and move them into some separate subdirectory like: drivers/net/ancient or drivers/net/antiques or drivers/net/archaic etc... so there's some clear designation that these crufty old drivers don't need to be touched anymore except for maybe when kernel wide changes occur.