Re: [PATCH v3] epoll.7: clarify the event distribution under edge-triggered mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



[TO += mtk]

Archive: <https://lore.kernel.org/linux-man/tencent_311E460546C884C26FB32E3C@xxxxxx/T/>

Hi,

On Wed, Jul 31, 2024 at 06:54:26PM GMT, 潘少 wrote:
> 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?

I understand it as:

	Since _even_ with edge-triggered epoll [and thus also with other
	epolls], multiple events can be generated ...

the stuff after the comma applied to at least more than one epoll typer.;
That's maybe why it's so generic.

However, I think a clarification like to one you suggest could be
appropriate in the page.  I've added Michael to this mail, who may be
better placed to help with these APIs.

Have a lovely day!
Alex

-- 
<https://www.alejandro-colomar.es/>

Attachment: signature.asc
Description: PGP signature


[Index of Archives]     [Kernel Documentation]     [Netdev]     [Linux Ethernet Bridging]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux Admin]     [Samba]

  Powered by Linux