lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-id: <20080125110942.GX18433@webber.adilger.int> Date: Fri, 25 Jan 2008 04:09:42 -0700 From: Andreas Dilger <adilger@....com> To: Zan Lynx <zlynx@....org> Cc: Theodore Tso <tytso@....EDU>, Adrian Bunk <bunk@...nel.org>, Bodo Eggert <7eggert@....de>, Alan Cox <alan@...rguk.ukuu.org.uk>, Valdis.Kletnieks@...edu, David Chinner <dgc@....com>, Valerie Henson <val@...consulting.com>, linux-fsdevel@...r.kernel.org, linux-ext4@...r.kernel.org, linux-kernel@...r.kernel.org, Ric Wheeler <ric@....com> Subject: Re: [RFC] Parallelize IO for e2fsck 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-ext4" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists