From: Paul P <ppak_98@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Fw: Re: unexpected extra pollout events from epoll
Date: Sun, 26 Oct 2008 13:19:44 -0700 (PDT) [thread overview]
Message-ID: <521981.87335.qm@web56305.mail.re3.yahoo.com> (raw)
> I'm not too familiar with the edge triggered mode, but
> you shouldn't be requesting EPOLLOUT notifications if you don't care
> about them (i.e. if you are not trying to write anything).
I am trying to write something, but I don't understand this behavior because it will screw up my notifications when I'm trying to see if I should write
more because of the extra notifications. Even before I started writing anything, I'm getting these epollout events which I was not expecting.
Paul
reply other threads:[~2008-10-26 20:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=521981.87335.qm@web56305.mail.re3.yahoo.com \
--to=ppak_98@yahoo.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.