From: Jeff Moyer <jmoyer@redhat.com>
To: Jens Axboe <axboe@kernel.dk>
Cc: "linux-block\@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: Re: [PATCH] io_uring: add support for IORING_REGISTER_FILES_UPDATE
Date: Fri, 04 Oct 2019 11:34:19 -0400 [thread overview]
Message-ID: <x49d0fcmsn8.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <a7bc8d7f-2379-7492-93af-6ca0353c5eab@kernel.dk> (Jens Axboe's message of "Fri, 4 Oct 2019 08:52:52 -0600")
Jens Axboe <axboe@kernel.dk> writes:
> Allows the application to remove/replace/add files to/from a file set.
> Passes in a struct:
>
> struct io_uring_files_update {
> __u32 offset;
> __s32 *fds;
> };
>
> that holds an array of fds, size of array passed in through the usual
> nr_args part of the io_uring_register() system call. The logic is as
> follows:
>
> 1) If ->fds[i] is -1, the existing file at i + ->offset is removed from
> the set.
> 2) If ->fds[i] is a valid fd, the existing file at i + ->offset is
> replaced with ->fds[i].
>
> For case #2, is the existing file is currently empty (fd == -1), the
> new fd is simply added to the array.
If I'm reading this (and the code) right, that means you can't add files
to a set. Wouldn't that be a useful thing to do, instead of just
replacing existing ones?
Can you post the man page update along with this?
Thanks,
Jeff
next prev parent reply other threads:[~2019-10-04 15:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-04 14:52 [PATCH] io_uring: add support for IORING_REGISTER_FILES_UPDATE Jens Axboe
2019-10-04 15:34 ` Jeff Moyer [this message]
2019-10-04 15:45 ` Jens Axboe
2019-10-04 16:03 ` Jeff Moyer
2019-10-04 16:11 ` Jens Axboe
2019-10-04 16:17 ` Jeff Moyer
2019-10-04 16:19 ` Jens Axboe
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=x49d0fcmsn8.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=axboe@kernel.dk \
--cc=linux-block@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.