From: Andy Grover <agrover@redhat.com>
To: dm-devel@redhat.com
Subject: [PATCH 0/5] Use uevent for thin pool events
Date: Wed, 16 Mar 2016 16:27:42 -0700 [thread overview]
Message-ID: <1458170867-429-1-git-send-email-agrover@redhat.com> (raw)
uevents both let us attach additional info to the event, and also
allow interested user processes to receive them without having to
create and manage threads to sit in DEV_WAIT ioctls for each target
we're interested in.
dm-mpath already supports generating uevents. This patchset
generalizes this code a little to allow another target to also
generate uevents, dm-thin, as a first step for what we might like to
do for all targets' events. DEV_WAIT ioctl support is unchanged.
Andy Grover (5):
dm: Do not export dm_send_uevents
dm: Move multipath-specific stuff out of dm-uevent.c
dm: Inline dm_build_path_uevent into dm_path_uevent
dm: Add uevent support for dm-thin
dm: Update dm-uevent.txt
Documentation/device-mapper/dm-uevent.txt | 48 ++++++++++++++++---
drivers/md/dm-mpath.c | 56 +++++++++++++++++++++++
drivers/md/dm-thin.c | 18 ++++++++
drivers/md/dm-uevent.c | 76 +++----------------------------
drivers/md/dm-uevent.h | 30 +++++++++---
drivers/md/dm.c | 1 +
6 files changed, 147 insertions(+), 82 deletions(-)
--
2.5.0
next reply other threads:[~2016-03-16 23:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 23:27 Andy Grover [this message]
2016-03-16 23:27 ` [PATCH 1/5] dm: Do not export dm_send_uevents Andy Grover
2016-03-16 23:27 ` [PATCH 2/5] dm: Move multipath-specific stuff out of dm-uevent.c Andy Grover
2016-03-16 23:27 ` [PATCH 3/5] dm: Inline dm_build_path_uevent into dm_path_uevent Andy Grover
2016-03-16 23:27 ` [PATCH 4/5] dm: Add uevent support for dm-thin Andy Grover
2016-03-16 23:27 ` [PATCH 5/5] dm: Update dm-uevent.txt Andy Grover
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=1458170867-429-1-git-send-email-agrover@redhat.com \
--to=agrover@redhat.com \
--cc=dm-devel@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).