[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZNx5Meh0doxdXs4H@Momo.fritz.box>
Date: Wed, 16 Aug 2023 09:22:25 +0200
From: Adam Sindelar <adam@...signal.io>
To: Hou Tao <houtao@...weicloud.com>
Cc: bpf@...r.kernel.org, Adam Sindelar <ats@...com>,
David Vernet <void@...ifault.com>,
Brendan Jackman <jackmanb@...gle.com>,
KP Singh <kpsingh@...omium.org>, linux-kernel@...r.kernel.org,
Alexei Starovoitov <ast@...nel.org>,
Florent Revest <revest@...omium.org>
Subject: Re: [PATCH bpf-next v5] libbpf: Expose API to consume one ring at a
time
On Fri, Jul 28, 2023 at 06:51:25PM +0800, Hou Tao wrote:
>
Hi, sorry for potentially dumb question, but should I do anything else
after someone acks it? This is a minor patch for a userland component,
but it's really helpful IMO - is anything preventing this getting merged
at this point?
Thanks,
Adam
> On 7/28/2023 5:33 PM, Adam Sindelar wrote:
> > We already provide ring_buffer__epoll_fd to enable use of external
> > polling systems. However, the only API available to consume the ring
> > buffer is ring_buffer__consume, which always checks all rings. When
> > polling for many events, this can be wasteful.
> >
> > Signed-off-by: Adam Sindelar <adam@...signal.io>
>
> Acked-by: Hou Tao <houtao1@...wei.com>
>
Powered by blists - more mailing lists