From mboxrd@z Thu Jan 1 00:00:00 1970 From: Theodore Tso Subject: Re: Read/write counts Date: Mon, 4 Jun 2007 16:00:03 -0400 Message-ID: <20070604200003.GD19224@thunk.org> References: <20070604163327.GR5181@schatzie.adilger.int> <20070604170223.GF23968@parisc-linux.org> <20070604183342.GC19224@thunk.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Matthew Wilcox , Bryan Henderson , Andreas Dilger , "David H. Lynch Jr." , linux-fsdevel@vger.kernel.org To: Roman Zippel Return-path: Received: from thunk.org ([69.25.196.29]:40040 "EHLO thunker.thunk.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760708AbXFDUA3 (ORCPT ); Mon, 4 Jun 2007 16:00:29 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Mon, Jun 04, 2007 at 08:57:16PM +0200, Roman Zippel wrote: > That's the last discussion about signals and I/O I can remember: > http://www.ussg.iu.edu/hypermail/linux/kernel/0208.0/0188.html Well, I think Linus was saying that we have to do both (where the signal interrupts and where it doesn't), and I agree with that: There are enough reasons to discourage people from using uninterruptible sleep ("this f*cking application won't die when the network goes down") that I don't think this is an issue. We need to handle both cases, and ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ while we can expand on the two cases we have now, we can't remove them. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Fortunately, although the -ERESTARTSYS framework is a little awkward (and people can shoot arrows at me for creating it 15 year ago :-), we do have a way of supporting both styles without _too_ much pain. - Ted