RFC dm-netlink events
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest3 of 4 patches 1 replyIn review
3 of 4 patches are in this archive. The cover letter announces 4.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/4 | dm-netlink skeleton supportdrivers/ drivers/ drivers/ +1 more | +154 | 0 replies | |
| 3/4 | dm-mpath calls to dm-netlinkdrivers/ drivers/ drivers/ | +11 | 0 replies | |
| 4/4 | Sample user space program (dm_nld)Makefile dm_nld.c dm_nld.h | +243 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH RFC 0/4] dm-netlink events
This is an update of my previous patch to add netlink event support to dm multipath. I have moved the dm netlink support out of a hardware handler and into a dm-netlink support file. I have changed the event messages to use netlink attributes which should allow for more flexibility in event message content over time.
This patch series adds a file called dm-netlink to the drivers/md directory to provide netlink support for dm events.
The skb mempool in this patch is derived / copied from drivers/scsi/scsi_transport_iscsi.c.
This patch series contains:
1 Core dm netlink support (dm-netlink).
2 Calls to dm-netlink for path failure / reinstate events. 3 A sample user space program to receive / display events (dm_nld).
I have ran path failure testing on a small config.
I ran the sample program as a 32 bit and 64 bit app against a 64 bit kernel.
Currently on path failures the blkerr is hard coded until that error support is complete.
Example out:
1.) Path failure.
Msg Type: 17 Recevied
Event Type: 1 Version: 6
[Event]: SEQNUM: 7, Time: Tue Nov 29 21:50:47 2005, DMNAME: 8:160, BLKERR:0x5a5a5a5a
2.) Path reinstate
Msg Type: 17 Recevied
Event Type: 2 Version: 6
[Event]: SEQNUM: 12, Time: Tue Nov 29 21:51:57 2005, DMNAME: 8:48
-andmike
--
Michael Anderson
[email protected]