From: "N. Jason Kleinbub" <jkleinbub@navtechinc.com>
To: Manfred Spraul <manfred@colorfullife.com>, linux-kernel@vger.kernel.org
Subject: Re: Selects on dirs/files.
Date: Tue, 13 Feb 2001 14:53:52 -0500 [thread overview]
Message-ID: <3A8990D0.3070209@navtechinc.com> (raw)
In-Reply-To: <3A894282.5070909@navtechinc.com> <3A8949B5.6BEDA269@colorfullife.com>
Manfred Spraul wrote:
> "N. Jason Kleinbub" wrote:
>> People,
>>
>> Not sure where to go from here but ....
>>
>> ( Yes I have read the FAQ )=
>>
>> For practical reasons, I have created some modification to the
>> Linux kernel. These changes were to make our implementation of
>> software more convenient (elegant). Essentially, I have modified the
>> select() calls to allow the non-trivial use of directories as an 'fd'.
>>
> Have you checked the F_NOTIFY fcntl()?
>
> If yes, what's the difference between your patch and F_NOTIFY?
The biggest impediment that I saw with F_NOTIFY was the inability
to distinguish _which_ directory generated the signal. This was
especially problematic for multithreaded apps. Also I would have
a chance of missing the signal if they pile ontop of each other.
Everytime I was interupted from my sleep() by a signal I would
have to scan _each_ directory to find the next file.
I admit, however, that the current F_NOTIFY has more functionality
then the current select().
Plus, for our programmers, it is a stylistic choice. They prefer,
and better understand, using select()/poll() versus signal io.
prev parent reply other threads:[~2001-02-13 19:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-13 14:19 Selects on dirs/files N. Jason Kleinbub
2001-02-13 14:50 ` Manfred Spraul
2001-02-13 19:53 ` N. Jason Kleinbub [this message]
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=3A8990D0.3070209@navtechinc.com \
--to=jkleinbub@navtechinc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=manfred@colorfullife.com \
/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.