io-uring.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: linux-kernel@vger.kernel.org, io-uring@vger.kernel.org
Subject: Re: [PATCH liburing v2 0/5] liburing: add helpers to enable/disable eventfd notifications
Date: Wed, 20 May 2020 11:12:39 -0600	[thread overview]
Message-ID: <f910cc65-9075-0e54-c4aa-656fb073d626@kernel.dk> (raw)
In-Reply-To: <20200520170714.68156-1-sgarzare@redhat.com>

On 5/20/20 11:07 AM, Stefano Garzarella wrote:
> This series is based on top of a new IORING_CQ_EVENTFD_DISABLED
> flag available in the CQ ring flags.
> 
> I added io_uring_cq_eventfd_enabled() to get the status of eventfd
> notifications, and io_uring_cq_eventfd_toggle() to disable/enabled
> eventfd notifications.
> 
> I updated man pages and I added a eventfd-disable.c test case.
> 
> v1 -> v2:
>   - renamed io_uring_cq_eventfd_toggle()
>   - return EOPNOTSUPP only if we need to change the flag

Applied, thanks.

-- 
Jens Axboe


      parent reply	other threads:[~2020-05-20 17:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-20 17:07 [PATCH liburing v2 0/5] liburing: add helpers to enable/disable eventfd notifications Stefano Garzarella
2020-05-20 17:07 ` [PATCH liburing v2 1/5] Add CQ ring 'flags' field Stefano Garzarella
2020-05-20 17:07 ` [PATCH liburing v2 2/5] man/io_uring_setup.2: add 'flags' field in the struct io_cqring_offsets Stefano Garzarella
2020-05-20 17:07 ` [PATCH liburing v2 3/5] Add helpers to set and get eventfd notification status Stefano Garzarella
2020-05-20 17:07 ` [PATCH liburing v2 4/5] man/io_uring_register.2: add IORING_CQ_EVENTFD_DISABLED description Stefano Garzarella
2020-05-20 17:07 ` [PATCH liburing v2 5/5] Add test/eventfd-disable.c test case Stefano Garzarella
2020-05-20 17:12 ` Jens Axboe [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=f910cc65-9075-0e54-c4aa-656fb073d626@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=io-uring@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sgarzare@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).