From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: syncing the disks when entering sleep Date: Thu, 11 Feb 2010 16:00:49 +0100 Message-ID: <20100211150049.GB1434@ucw.cz> References: <76FA3B279DD9DA48896E2B404944957204E0B241@USA7061MS02.na.xerox.net> <201002101134.23851.rjw@sisk.pl> <20100210133118.GA31861@atrey.karlin.mff.cuni.cz> <201002102019.26518.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <201002102019.26518.rjw@sisk.pl> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: "Rafael J. Wysocki" Cc: linux-pm@lists.linux-foundation.org, Nigel Cunningham , "Leisner, Martin" List-Id: linux-pm@vger.kernel.org > > Really? If so then it is misdesigned. > > > > Before the "don't sync" proposal, it was okay to have multiple > > power managers. > > > > Actually I have three on zaurus. There's in-kernel suspend on battery > > critical, then there's somehing userspace in desktop environment, and > > then I'm triggering suspends by hand using echo. > > To be precise, 1 and 3 are things that override the power manager. > > And if you override the power manager, you're supposed to know what you're > doing, aren't you? I know what I'm doing, but I'd prefer traps not being set for me. > > > So really, I don't see anything wrong with a knob that will turn the kernel > > > sync off entirely, because that basically means "my user space is > > > not broken". > > > > Because, very easily, parts of my users space may be broken. > > How exactly would they be broken? I have 3 power managers. You called that broken before. How is power manager expected to work on zaurus, which suspends from kernel on battery critical? echo no > sync; sync; echo mem > state; echo yes > sync? Its still racy.. > Why don't we just assume that the user who sets the knob knows what he's doing? > Because better alternatives exist. Like 'echo mem:nosync > state'. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html