From: Martin Wilck <mwilck@suse.com>
To: tang.junhui@zte.com.cn
Cc: dm-devel@redhat.com
Subject: Re: Improve processing efficiency for addition and deletion of multipath devices
Date: Fri, 18 Nov 2016 08:39:08 +0100 [thread overview]
Message-ID: <1479454748.25031.4.camel@suse.com> (raw)
In-Reply-To: <OF3A4A70D0.4D2612E4-ON4825806F.00029856-4825806F.0005B3C7@zte.com.cn>
Hi Tang,
On Fri, 2016-11-18 at 09:02 +0800, tang.junhui@zte.com.cn wrote:
>
> we are more concerned
> about the more common situation like addition or deletion devices
> when
> iSCSI login/logout or FC link up/down with many iSCSI or FC links
> in
> each LUN. At this situation we may receive many uevents from
> different
> paths of the same LUN device, we want merge these uevents to one
> and
> process them together.
I'm not arguing against that. But consider what you'd do if you have to
process the series of uevents [ 1 "add sda", 2 "add sdb", 3 "del sda",
4 "add sdc", 5 "del sdb", 6 "add sda" ]. If you merge these, assuming
all belong to the same multipath map, what would be your action? I
would set up a map with sda and sdc, using the device properties from
event 4 and 6. That means that the rest of the events has been
"filtered" out. All else would mean repeated map loads for the same
multipath map, which is what we want to avoid. Agreed?
Regards,
Martin
--
Dr. Martin Wilck <mwilck@suse.com>, Tel. +49 (0)911 74053 2107
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton
HRB 21284 (AG Nürnberg)
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2016-11-18 7:39 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-16 1:46 Improve processing efficiency for addition and deletion of multipath devices tang.junhui
2016-11-16 7:53 ` Hannes Reinecke
2016-11-16 8:45 ` tang.junhui
2016-11-16 9:49 ` Martin Wilck
2016-11-17 1:41 ` tang.junhui
2016-11-17 10:48 ` Martin Wilck
2016-11-18 1:02 ` tang.junhui
2016-11-18 7:39 ` Martin Wilck [this message]
2016-11-18 8:24 ` tang.junhui
2016-11-18 8:30 ` Martin Wilck
2016-11-18 8:56 ` tang.junhui
2016-11-18 9:12 ` tang.junhui
2016-11-21 18:19 ` Benjamin Marzinski
2016-11-18 22:26 ` Benjamin Marzinski
2016-11-23 1:08 ` tang.junhui
2016-11-29 9:07 ` Zdenek Kabelac
2016-11-29 10:13 ` tang.junhui
2016-11-24 9:21 ` Martin Wilck
2016-11-28 18:46 ` Benjamin Marzinski
2016-11-29 6:47 ` Hannes Reinecke
2016-11-29 8:02 ` Martin Wilck
2016-11-29 8:10 ` Zdenek Kabelac
2016-11-29 8:16 ` Martin Wilck
2016-11-29 8:24 ` Zdenek Kabelac
2016-11-29 17:25 ` Benjamin Marzinski
2016-11-29 7:57 ` Martin Wilck
2016-11-29 17:41 ` Benjamin Marzinski
-- strict thread matches above, loose matches on Subject: below --
2016-11-28 2:19 tang.junhui
2016-11-28 10:05 ` Hannes Reinecke
2016-11-28 16:07 ` Benjamin Marzinski
2016-11-28 16:26 ` Zdenek Kabelac
2016-11-28 10:06 ` Zdenek Kabelac
2016-11-28 10:42 ` Hannes Reinecke
2016-11-28 11:51 ` Zdenek Kabelac
2016-11-28 12:06 ` Peter Rajnoha
2016-11-28 12:08 ` Hannes Reinecke
2016-11-28 12:23 ` Peter Rajnoha
2016-11-28 12:55 ` Zdenek Kabelac
2016-11-28 17:22 ` Benjamin Marzinski
2016-11-29 9:34 ` Zdenek Kabelac
2016-11-28 10:28 ` Martin Wilck
2016-11-28 17:31 ` Benjamin Marzinski
2016-11-29 7:52 ` Martin Wilck
2016-11-29 19:21 ` Benjamin Marzinski
2016-11-28 15:25 ` Benjamin Marzinski
2016-11-28 15:37 ` Hannes Reinecke
2016-12-01 1:16 ` tang.junhui
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=1479454748.25031.4.camel@suse.com \
--to=mwilck@suse.com \
--cc=dm-devel@redhat.com \
--cc=tang.junhui@zte.com.cn \
/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.