From: Davide Libenzi <davidel@xmailserver.org>
To: Pavel Pisa <pisa@cmp.felk.cvut.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [patch 1/2] epoll fix own poll()
Date: Fri, 30 Jan 2009 10:40:51 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.1.10.0901301034370.31459@alien.or.mcafeemobile.com> (raw)
In-Reply-To: <200901301042.05333.pisa@cmp.felk.cvut.cz>
On Fri, 30 Jan 2009, Pavel Pisa wrote:
> I have seen the reason exactly when I have sent the e-mail
> and switched computer off at the night.
>
> The reason is simple and it is caused by debugging print in each
> loop in my application and by way how poll concept is implemented
> in the kernel.
Yes, this is a known thing. Like I already told you yesterday, calling it
a "spurious" event. So you code *is* generating a spurios event to the
tty, with a write.
Unfortunately this is how Linux poll subsystem works. But things can be
improved, w/out any revolution.
I already have patches to send Andrew-ward, that (gradually) uses the
wakeup "key" to report event that really happened, during the wakeup call.
This will allow the epoll callback to avoid epoll waiters wakeups, when
events do not match the interest mask.
- Davide
prev parent reply other threads:[~2009-01-30 18:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 20:54 Davide Libenzi
2009-01-27 20:59 ` Davide Libenzi
2009-01-29 8:01 ` Andrew Morton
2009-01-29 18:16 ` Davide Libenzi
2009-01-29 18:27 ` Andrew Morton
2009-01-29 18:32 ` Davide Libenzi
2009-01-29 18:37 ` Andrew Morton
2009-01-29 18:43 ` Davide Libenzi
2009-01-30 2:29 ` Pavel Pisa
2009-01-30 2:52 ` Davide Libenzi
2009-01-30 7:41 ` Davide Libenzi
2009-01-30 9:42 ` Pavel Pisa
2009-01-30 18:40 ` Davide Libenzi [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=alpine.DEB.1.10.0901301034370.31459@alien.or.mcafeemobile.com \
--to=davidel@xmailserver.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pisa@cmp.felk.cvut.cz \
/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
all inboxes | Powered by JetHome®