Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760139AbYAYUYe (ORCPT ); Fri, 25 Jan 2008 15:24:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1759713AbYAYUYD (ORCPT ); Fri, 25 Jan 2008 15:24:03 -0500 Received: from idcmail-mo1so.shaw.ca ([24.71.223.10]:61457 "EHLO pd4mo3so.prod.shaw.ca" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759563AbYAYUX7 (ORCPT ); Fri, 25 Jan 2008 15:23:59 -0500 Date: Fri, 25 Jan 2008 04:09:42 -0700 From: Andreas Dilger Subject: Re: [RFC] Parallelize IO for e2fsck In-reply-to: <1201220742.7557.10.camel@localhost> To: Zan Lynx Cc: Theodore Tso , Adrian Bunk , Bodo Eggert <7eggert@gmx.de>, Alan Cox , Valdis.Kletnieks@vt.edu, David Chinner , Valerie Henson , linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, Ric Wheeler Mail-followup-to: Zan Lynx , Theodore Tso , Adrian Bunk , Bodo Eggert <7eggert@gmx.de>, Alan Cox , Valdis.Kletnieks@vt.edu, David Chinner , Valerie Henson , linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org, Ric Wheeler Message-id: <20080125110942.GX18433@webber.adilger.int> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline X-GPG-Key: 1024D/0D35BED6 X-GPG-Fingerprint: 7A37 5D79 BF1B CECA D44F 8A29 A488 39F5 0D35 BED6 References: <9Mo9w-7Ws-23@gated-at.bofh.it> <9OdWm-7uN-25@gated-at.bofh.it> <9Oi9A-5EJ-3@gated-at.bofh.it> <9OiMg-6IC-1@gated-at.bofh.it> <9OlqL-2xG-3@gated-at.bofh.it> <9Orda-3ub-45@gated-at.bofh.it> <20080124230809.GA29120@does.not.exist> <20080124234037.GJ15858@mit.edu> <1201220742.7557.10.camel@localhost> User-Agent: Mutt/1.5.17 (2007-11-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 874 Lines: 22 On Jan 24, 2008 17:25 -0700, Zan Lynx wrote: > Have y'all been following the /dev/mem_notify patches? > http://article.gmane.org/gmane.linux.kernel/628653 Having the notification be via poll() is a very restrictive processing model. Having the notification be via a signal means that any kind of process (and not just those that are event loop driven) can register a callback at some arbitrary point in the code and be notified. I don't object to the poll() interface, but it would be good to have a signal mechanism also. Cheers, Andreas -- Andreas Dilger Sr. Staff Engineer, Lustre Group Sun Microsystems of Canada, Inc. -- 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/