From: Jason Gunthorpe <jgg@ziepe.ca>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: Grzegorz Jaszczyk <jaz@semihalf.com>,
Christian Brauner <brauner@kernel.org>,
linux-fsdevel@vger.kernel.org, linux-aio@kvack.org,
linux-usb@vger.kernel.org,
Matthew Rosato <mjrosato@linux.ibm.com>,
Paul Durrant <paul@xen.org>, Tom Rix <trix@redhat.com>,
Jason Wang <jasowang@redhat.com>,
dri-devel@lists.freedesktop.org, Michal Hocko <mhocko@kernel.org>,
linux-mm@kvack.org, Kirti Wankhede <kwankhede@nvidia.com>,
Paolo Bonzini <pbonzini@redhat.com>, Jens Axboe <axboe@kernel.dk>,
Vineeth Vijayan <vneethv@linux.ibm.com>,
Diana Craciun <diana.craciun@oss.nxp.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Shakeel Butt <shakeelb@google.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Leon Romanovsky <leon@kernel.org>,
Harald Freudenberger <freude@linux.ibm.com>,
Fei Li <fei1.li@intel.com>,
x86@kernel.org, Roman Gushchin <roman.gushchin@lin>
Subject: Re: [PATCH 0/2] eventfd: simplify signal helpers
Date: Mon, 17 Jul 2023 19:12:16 -0300 [thread overview]
Message-ID: <ZLW8wEzkhBxd0O0L@ziepe.ca> (raw)
In-Reply-To: <20230717130831.0f18381a.alex.williamson@redhat.com>
On Mon, Jul 17, 2023 at 01:08:31PM -0600, Alex Williamson wrote:
> What would that mechanism be? We've been iterating on getting the
> serialization and buffering correct, but I don't know of another means
> that combines the notification with a value, so we'd likely end up with
> an eventfd only for notification and a separate ring buffer for
> notification values.
All FDs do this. You just have to make a FD with custom
file_operations that does what this wants. The uAPI shouldn't be able
to tell if the FD is backing it with an eventfd or otherwise. Have the
kernel return the FD instead of accepting it. Follow the basic design
of eg mlx5vf_save_fops
Jason
--
To unsubscribe, send a message with 'unsubscribe linux-aio' in
the body to majordomo@kvack.org. For more info on Linux AIO,
see: http://www.kvack.org/aio/
Don't email: <a href=mailto:"aart@kvack.org">aart@kvack.org</a>
next prev parent reply other threads:[~2023-07-17 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230630155936.3015595-1-jaz@semihalf.com>
2023-07-14 7:05 ` [PATCH 0/2] eventfd: simplify signal helpers Christian Brauner
2023-07-14 15:24 ` Jason Gunthorpe
2023-07-17 8:29 ` Grzegorz Jaszczyk
2023-07-17 19:08 ` Alex Williamson
2023-07-17 22:12 ` Jason Gunthorpe [this message]
2023-07-17 22:52 ` Alex Williamson
2023-07-18 15:56 ` Jason Gunthorpe
2023-07-13 10:05 Christian Brauner
2023-07-13 17:10 ` Alex Williamson
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=ZLW8wEzkhBxd0O0L@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=agordeev@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=diana.craciun@oss.nxp.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=fei1.li@intel.com \
--cc=freude@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=jasowang@redhat.com \
--cc=jaz@semihalf.com \
--cc=kwankhede@nvidia.com \
--cc=leon@kernel.org \
--cc=linux-aio@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-usb@vger.kernel.org \
--cc=mhocko@kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=roman.gushchin@lin \
--cc=shakeelb@google.com \
--cc=trix@redhat.com \
--cc=vneethv@linux.ibm.com \
--cc=x86@kernel.org \
--cc=xuanzhuo@linux.alibaba.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