From: Mike Anderson <andmike@us.ibm.com>
To: dm-devel@redhat.com
Subject: [PATCH 0/2] dm-netlink events (update)
Date: Thu, 9 Feb 2006 07:40:09 -0800 [thread overview]
Message-ID: <20060209154009.GA29591@us.ibm.com> (raw)
This is another update of my previous patch to add netlink event support to dm.
The skb mempool in this patch is derived from:
drivers/scsi/scsi_transport_iscsi.c.
This patch series contains:
1 dm-netlink skeleton support.
2 The netlink support to dm-netlink. Add init calls and send on path
failure and reinstate events.
I have ran path failure testing on a small config.
Output:
1.) Path failure.
Msg Type: 17 Recevied
Event Type: 1 Version: 8
[Event]: MDNAME: 253:5, SEQNUM: 3, Time: Thu Feb 9 15:33:41 2006, DMNAME:
65:112, VLDPTHS: 0x3
2.) Path reinstate.
Msg Type: 17 Recevied
Event Type: 2 Version: 8
[Event]: MDNAME: 253:5, SEQNUM: 4, Time: Thu Feb 9 15:38:33 2006, DMNAME:
65:112, VLDPTHS: 0x4
-andmike
--
Michael Anderson
andmike@us.ibm.com
next reply other threads:[~2006-02-09 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 15:40 Mike Anderson [this message]
2006-02-09 15:41 ` [PATCH 1/2] dm-netlink events skeleton support (update) Mike Anderson
2006-02-09 15:43 ` [PATCH 2/2] dm-netlink events netlink calls (update) Mike Anderson
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=20060209154009.GA29591@us.ibm.com \
--to=andmike@us.ibm.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 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.