From: Jason Gunthorpe <[email protected]>
To: Alex Williamson <[email protected]>
Cc: Grzegorz Jaszczyk <[email protected]>,
Christian Brauner <[email protected]>,
[email protected], [email protected],
[email protected],
Matthew Rosato <[email protected]>,
Paul Durrant <[email protected]>, Tom Rix <[email protected]>,
Jason Wang <[email protected]>,
[email protected], Michal Hocko <[email protected]>,
[email protected], Kirti Wankhede <[email protected]>,
Paolo Bonzini <[email protected]>, Jens Axboe <[email protected]>,
Vineeth Vijayan <[email protected]>,
Diana Craciun <[email protected]>,
Alexander Gordeev <[email protected]>,
Xuan Zhuo <[email protected]>,
Shakeel Butt <[email protected]>,
Vasily Gorbik <[email protected]>,
Leon Romanovsky <[email protected]>,
Harald Freudenberger <[email protected]>,
Fei Li <[email protected]>,
[email protected], Roman Gushchin <[email protected]>,
Halil Pasic <[email protected]>, Ingo Molnar <[email protected]>,
[email protected],
Christian Borntraeger <[email protected]>,
[email protected], Zhi Wang <[email protected]>,
Wu Hao <[email protected]>, Jason Herne <[email protected]>,
Eric Farman <[email protected]>,
Dave Hansen <[email protected]>,
Andrew Donnellan <[email protected]>,
Arnd Bergmann <[email protected]>,
[email protected], Heiko Carstens <[email protected]>,
Johannes Weiner <[email protected]>,
[email protected], Eric Auger <[email protected]>,
Borislav Petkov <[email protected]>,
[email protected], Rodrigo Vivi <[email protected]>,
[email protected], Thomas Gleixner <[email protected]>,
[email protected],
[email protected], [email protected],
[email protected], Tony Krowiak <[email protected]>,
Tvrtko Ursulin <[email protected]>,
Pavel Begunkov <[email protected]>,
Sean Christopherson <[email protected]>,
Oded Gabbay <[email protected]>,
Muchun Song <[email protected]>,
Peter Oberparleiter <[email protected]>,
[email protected], [email protected],
Benjamin LaHaise <[email protected]>,
"Michael S. Tsirkin" <[email protected]>,
Sven Schnelle <[email protected]>,
Greg Kroah-Hartman <[email protected]>,
Frederic Barrat <[email protected]>,
Moritz Fischer <[email protected]>,
Vitaly Kuznetsov <[email protected]>,
David Woodhouse <[email protected]>,
Xu Yilun <[email protected]>, Dominik Behr <[email protected]>,
Marcin Wojtas <[email protected]>
Subject: Re: [PATCH 0/2] eventfd: simplify signal helpers
Date: Mon, 17 Jul 2023 19:12:16 -0300 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
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
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] <[email protected]>
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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