From: Mike Snitzer <snitzer@redhat.com>
To: Andy Grover <agrover@redhat.com>
Cc: dm-devel@redhat.com, mpatocka@redhat.com
Subject: Re: [PATCH 0/3] poll()able DM events
Date: Tue, 9 May 2017 17:14:36 -0400 [thread overview]
Message-ID: <20170509211436.GA1439@redhat.com> (raw)
In-Reply-To: <20170509191028.6898-1-agrover@redhat.com>
On Tue, May 09 2017 at 3:10pm -0400,
Andy Grover <agrover@redhat.com> wrote:
> Hi Mike,
>
> We've been working off-list to develop a method of getting DM events
> that is reliable, and also can monitor events from multiple DM devices
> from a single thread.
>
> In short, these enable an open file descriptor to /dev/mapper/control
> to be polled. If the fd indicates POLLIN, some DM device has
> experienced an event. Figuring out which is made easier by adding
> event_nr in a backwards-compatible way to DM_LIST_DEVICES, so
> userspace can compare against previously seen per-device
> event_nrs. A new ioctl is also added, to rearm the fd so it may be
> re-poll()ed. See individual patch commitlogs for more details.
>
> Thanks to Mikulas for redeveloping earlier versions into this patchset,
> as well as the other RH LVM devs who provided early internal feedback!
I've picked this patchset up for 4.13 but this branch will likely see
quite a few more rebases until 4.12-rcX stabilizes:
https://git.kernel.org/pub/scm/linux/kernel/git/device-mapper/linux-dm.git/log/?h=for-4.13/dm
I tweaked headers slightly and move the declaration of the variable used
in the last commit to be outside the loop.
Thought about splitting the additional 'struct file *filp' arg being
sprinkled all over in the 2nd commit, into a separate earlier commit,
but just left it as is in the end.
Mike
next prev parent reply other threads:[~2017-05-09 21:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-09 19:10 [PATCH 0/3] poll()able DM events Andy Grover
2017-05-09 19:10 ` [PATCH 1/3] dm: a basic support for using the select or poll function Andy Grover
2017-05-11 9:39 ` Martin Wilck
2017-05-11 9:43 ` Martin Wilck
2017-05-11 13:21 ` Mike Snitzer
2017-05-11 18:10 ` Andy Grover
2017-05-11 19:49 ` Martin Wilck
2017-05-11 20:21 ` Alasdair G Kergon
2017-05-11 20:45 ` Martin Wilck
2017-05-11 21:38 ` Alasdair G Kergon
2017-05-11 19:30 ` Martin Wilck
2017-05-11 21:46 ` Andy Grover
2017-05-12 6:48 ` Martin Wilck
2017-05-11 21:50 ` Alasdair G Kergon
2017-05-12 15:52 ` Mikulas Patocka
2017-05-09 19:10 ` [PATCH 2/3] dm-ioctl: add a new DM_DEV_ARM_POLL ioctl Andy Grover
2017-05-09 19:10 ` [PATCH 3/3] dm-ioctl: report event number in DM_LIST_DEVICES Andy Grover
2017-05-09 21:14 ` Mike Snitzer [this message]
2017-09-17 2:41 ` Eugene Syromiatnikov
2017-09-19 16:47 ` Andy Grover
2017-09-20 11:29 ` [PATCH] dm-ioctl: fix alignment of event number in the device list Mikulas Patocka
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=20170509211436.GA1439@redhat.com \
--to=snitzer@redhat.com \
--cc=agrover@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mpatocka@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 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.