Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S965153AbWLTRWW (ORCPT ); Wed, 20 Dec 2006 12:22:22 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S965154AbWLTRWW (ORCPT ); Wed, 20 Dec 2006 12:22:22 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:44139 "EHLO pentafluge.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965153AbWLTRWV (ORCPT ); Wed, 20 Dec 2006 12:22:21 -0500 Subject: Re: Network drivers that don't suspend on interface down From: Arjan van de Ven To: Olivier Galibert Cc: Matthew Garrett , linux-kernel@vger.kernel.org, netdev@vger.kernel.org In-Reply-To: <20061220164054.GA27938@dspnet.fr.eu.org> References: <200612191959.43019.david-b@pacbell.net> <20061220042648.GA19814@srcf.ucam.org> <200612192114.49920.david-b@pacbell.net> <20061220053417.GA29877@suse.de> <20061220055209.GA20483@srcf.ucam.org> <1166601025.3365.1345.camel@laptopd505.fenrus.org> <20061220125314.GA24188@srcf.ucam.org> <1166621931.3365.1384.camel@laptopd505.fenrus.org> <20061220152701.GA22928@dspnet.fr.eu.org> <1166628858.3365.1425.camel@laptopd505.fenrus.org> <20061220164054.GA27938@dspnet.fr.eu.org> Content-Type: text/plain Organization: Intel International BV Date: Wed, 20 Dec 2006 18:21:39 +0100 Message-Id: <1166635300.3365.1442.camel@laptopd505.fenrus.org> Mime-Version: 1.0 X-Mailer: Evolution 2.8.2.1 (2.8.2.1-2.fc6) Content-Transfer-Encoding: 7bit X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1403 Lines: 35 On Wed, 2006-12-20 at 17:40 +0100, Olivier Galibert wrote: > On Wed, Dec 20, 2006 at 04:34:17PM +0100, Arjan van de Ven wrote: > > 5 seconds is unfair and unrealistic though. The *hardware* negotiation > > before link is seen can easily take upto 45 seconds already. > > That's a network topology/hardware issue (spanning tree fun) that > > software or even the hardware in your PC can do nothing about. > > It's about ergonomics, not technical capabilities or fairness. not entirely. > > > > this means that the "power up time" needs to be at least 45 seconds, if > > it's then down 5 seconds inbetween... that's not real power savings. > > Then that means you can't have usable autodetection and power savings > at the same time. even if you have NO power savings you still don't meet your criteria. That's basic ethernet for you.... That's what I was trying to say; your criteria is unrealistic regardless of what the kernel does, ethernet already dictates 30 to 45 seconds there. -- if you want to mail me at work (you don't), use arjan (at) linux.intel.com Test the interaction between Linux and your BIOS via http://www.linuxfirmwarekit.org - 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/