Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753436AbbEHTwx (ORCPT ); Fri, 8 May 2015 15:52:53 -0400 Received: from 251.110.2.81.in-addr.arpa ([81.2.110.251]:46354 "EHLO lxorguk.ukuu.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751733AbbEHTww (ORCPT ); Fri, 8 May 2015 15:52:52 -0400 Date: Fri, 8 May 2015 20:52:33 +0100 From: One Thousand Gnomes To: Len Brown Cc: Alan Stern , "Rafael J. Wysocki" , Linux PM list , "linux-kernel@vger.kernel.org" , Len Brown Subject: Re: [PATCH 1/1] suspend: delete sys_sync() Message-ID: <20150508205233.72b9fae3@lxorguk.ukuu.org.uk> In-Reply-To: References: <20150508201310.5c4ccfaa@lxorguk.ukuu.org.uk> Organization: Intel Corporation X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.27; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1193 Lines: 27 > > Some of this however is crappy suspend/resume handling. If the suspend > > subsystem was doing its job then for the cases of timeout triggered > > suspend it would have triggered most of the disk writes ten seconds > > before it tried to suspend properly ;-) > > No problem, continue to use s2ram on your system -- and to the extent > that sync works, your data will be on disk. (sync reliability is a > different topic...) Ok let me ask the other obvious question. For all the mainstream distributions do their default tools and setup sync such that removing it from the kernel won't actually be noticable by users ? If the answer is yes, then I shall shut up and stop worrying 8) > Understand, however, there are systems which suspend/resume reliably > many times per second, making policy choice of having the kernel hard-code > a sys_sync() into the suspend path a bad idea. I'm aware of that - I have a very nice ASUS T100TA. Alan -- 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/