public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: 潘少 <i@andypan.me>
To: "Alejandro Colomar" <alx@kernel.org>
Cc: linux-man <linux-man@vger.kernel.org>,
	linux-api <linux-api@vger.kernel.org>
Subject: Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode
Date: Wed, 31 Jul 2024 18:54:26 +0800	[thread overview]
Message-ID: <tencent_311E460546C884C26FB32E3C@qq.com> (raw)
In-Reply-To: <2yb4zrih5esl3qldowd34ojg7mjq3xqjmqvq5bb5y6ru4x7rv5@p6ahw4ztu5cf>

Hi Alejandro,
> Since even with edge-triggered epoll, multiple events can be
> generated upon receipt of multiple chunks of data, the caller has
> the option to specify the EPOLLONESHOT flag, to tell epoll to
> disable the associated file descriptor after the receipt of an
> event with epoll_wait(2).  When the EPOLLONESHOT flag is
> specified, it is the caller's responsibility to rearm the file
> descriptor using epoll_ctl(2) with EPOLL_CTL_MOD.

This paragraph in man pages of epoll starts with "Since even with edge-triggered epoll", thus I assume the following sentences of "multiple events can be generated upon receipt of multiple chunks of data" and "that is, an event will be generated upon each receipt of a chunk of data" ought to be talking about EPOLLET naturally. Have I misunderstood something?

  reply	other threads:[~2024-07-31 10:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-30 10:48 [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode Andy Pan via B4 Relay
2024-07-31 10:39 ` Alejandro Colomar
2024-07-31 10:54   ` 潘少 [this message]
2024-07-31 11:07     ` Alejandro Colomar
     [not found]       ` <DD88B2A8DED5353D+137af5bf-158d-4e1e-b4ae-c4262434f8a6@Spark>
2024-07-31 11:21         ` Alejandro Colomar
2024-07-31 15:22           ` 潘少
2024-08-01 11:40             ` 潘少
2024-07-31 11:21       ` 潘少

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=tencent_311E460546C884C26FB32E3C@qq.com \
    --to=i@andypan.me \
    --cc=alx@kernel.org \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-man@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox