From: "KOSAKI Motohiro" <kosaki.motohiro@gmail.com>
To: "Zan Lynx" <zlynx@acm.org>, "Andreas Dilger" <adilger@sun.com>
Cc: "Theodore Tso" <tytso@mit.edu>, "Adrian Bunk" <bunk@kernel.org>,
"Bodo Eggert" <7eggert@gmx.de>,
"Alan Cox" <alan@lxorguk.ukuu.org.uk>,
Valdis.Kletnieks@vt.edu, "David Chinner" <dgc@sgi.com>,
"Valerie Henson" <val@vahconsulting.com>,
linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, "Ric Wheeler" <ric@emc.com>
Subject: Re: [RFC] Parallelize IO for e2fsck
Date: Sat, 26 Jan 2008 20:56:24 +0900 [thread overview]
Message-ID: <2f11576a0801260356tfbf3078w5ff98e8909e07b6c@mail.gmail.com> (raw)
In-Reply-To: <1201308912.7784.6.camel@localhost>
> The commentary on the mem_notify threads claimed that the signal is
> easily provided by setting up the file handle for SIGIO.
BTW:
Of cource, you can receive any signal instead SIGIO by use fcntl(F_SETSIG) :-)
next prev parent reply other threads:[~2008-01-26 11:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <9Mo9w-7Ws-25@gated-at.bofh.it>
[not found] ` <9Mo9w-7Ws-23@gated-at.bofh.it>
[not found] ` <9OdWm-7uN-25@gated-at.bofh.it>
[not found] ` <9Oi9A-5EJ-3@gated-at.bofh.it>
[not found] ` <9OiMg-6IC-1@gated-at.bofh.it>
[not found] ` <9OlqL-2xG-3@gated-at.bofh.it>
[not found] ` <9Orda-3ub-45@gated-at.bofh.it>
2008-01-24 17:32 ` [RFC] Parallelize IO for e2fsck Bodo Eggert
[not found] ` <E1JI5vz-0001GG-Vs@be1.7eggert.dyndns.org>
2008-01-24 22:07 ` Andreas Dilger
2008-01-24 23:08 ` Adrian Bunk
2008-01-24 23:40 ` Theodore Tso
2008-01-25 0:25 ` Zan Lynx
2008-01-25 11:09 ` Andreas Dilger
2008-01-26 0:55 ` Zan Lynx
2008-01-26 11:56 ` KOSAKI Motohiro [this message]
2008-01-25 18:03 ` Bryan Henderson
2008-01-25 23:01 ` Bodo Eggert
2008-01-26 1:55 ` Bryan Henderson
2008-01-26 13:21 ` Theodore Tso
2008-01-26 12:32 ` KOSAKI Motohiro
[not found] ` <2f11576a0801260432y4405d817p6ef4005d06189654@mail.gmail.com>
2008-01-26 13:55 ` Kernel Event Notifications (was: [RFC] Parallelize IO for e2fsck) Al Boldi
2008-01-26 16:01 ` KOSAKI Motohiro
2008-01-28 23:23 ` Jon Masters
[not found] ` <1201562634.5412.70.camel@jcmlaptop>
2008-02-03 13:38 ` KOSAKI Motohiro
[not found] <70b6f0bf0801161322k2740a8dch6a0d6e6e112cd2d0@mail.gmail.com>
2008-01-16 21:30 ` [RFC] Parallelize IO for e2fsck Valerie Henson
2008-01-18 1:15 ` David Chinner
2008-01-18 1:43 ` Valerie Henson
2008-01-21 23:00 ` Andreas Dilger
2008-01-22 3:38 ` David Chinner
2008-01-22 4:17 ` Valdis.Kletnieks
2008-01-22 7:00 ` Andreas Dilger
2008-01-22 13:05 ` Alan Cox
[not found] ` <20080122144052.GC17804@mit.edu>
[not found] ` <20080128193005.GC4032@ucw.cz>
2008-01-28 19:56 ` Theodore Tso
2008-01-29 8:29 ` david
[not found] ` <20080128200105.GA4719@ucw.cz>
2008-02-03 13:51 ` KOSAKI Motohiro
2008-01-22 7:05 ` Andreas Dilger
2008-01-22 8:16 ` David Chinner
2008-01-22 17:42 ` Bryan Henderson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2f11576a0801260356tfbf3078w5ff98e8909e07b6c@mail.gmail.com \
--to=kosaki.motohiro@gmail.com \
--cc=7eggert@gmx.de \
--cc=Valdis.Kletnieks@vt.edu \
--cc=adilger@sun.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bunk@kernel.org \
--cc=dgc@sgi.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ric@emc.com \
--cc=tytso@mit.edu \
--cc=val@vahconsulting.com \
--cc=zlynx@acm.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).