From: Vitaly Luban <vitaly@luban.org>
To: Dan Kegel <dank@kegel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH][RFC] Signal-per-fd for RT signals
Date: Sat, 15 Sep 2001 19:35:24 -0700 [thread overview]
Message-ID: <3BA40FEC.A6E0557E@luban.org> (raw)
In-Reply-To: <3BA2AFFF.C7B8C4DF@kegel.com> <3BA2E144.FB0E5D55@luban.org> <3BA2E99A.1134E382@kegel.com> <3BA350A7.7D39FC23@kegel.com> <3BA3C61A.DED5A27A@luban.org> <3BA3D10B.FE3C6C79@kegel.com>
[-- Attachment #1: Type: text/plain, Size: 847 bytes --]
Dan Kegel wrote:
> But I doubt very much that SIGIO style readiness notification will ever
> be used with files. aio_{read,write} style completion notification is
> much more appropriate for file I/O, and my proposal (if I make it) will not
> affect that.
Well, when I have an app, that deals primarily with network I/O, and, at the same time
has some file I/O, it's only logical to have all I/O handling within the same event
loop, and if loop is RT-signals based...
> Thanks again for creating and maintaining your patch! I look forward to
> stress-testing the next version.
Could you please try attached one? It's mostly untested, but my home site
will be down next week.
And thank you for your efforts also :)
I'm looking forward to see a test case, all I could come up with happily
runs on the old version.
Thanks again,
Vitaly.
[-- Attachment #2: one-sig-perfd-2.4.9.patch.gz --]
[-- Type: application/x-gzip, Size: 2289 bytes --]
next prev parent reply other threads:[~2001-09-16 2:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-15 1:33 [PATCH][RFC] Signal-per-fd for RT signals Dan Kegel
2001-09-15 5:04 ` Vitaly Luban
2001-09-15 5:39 ` Dan Kegel
2001-09-15 12:59 ` spin_lock_bh() usage check, please (was: [PATCH][RFC] Signal-per-fd for RT signals) Dan Kegel
2001-09-15 21:20 ` Vitaly Luban
2001-09-15 22:07 ` Dan Kegel
2001-09-16 2:35 ` Vitaly Luban [this message]
2001-09-16 3:51 ` [PATCH][RFC] Signal-per-fd for RT signals Dan Kegel
2001-09-22 23:30 ` [PATCH][RFC] Signal-per-fd for RT signals; write_lock_bh(file_lock)? Dan Kegel
-- strict thread matches above, loose matches on Subject: below --
2001-05-19 2:04 [PATCH][RFC] Signal-per-fd for RT signals Vitaly Luban
2001-05-19 21:38 ` Gerold Jury
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=3BA40FEC.A6E0557E@luban.org \
--to=vitaly@luban.org \
--cc=dank@kegel.com \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.