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: Thu, 17 Nov 2016 11:48:32 +0100 [thread overview]
Message-ID: <1479379712.14706.23.camel@suse.com> (raw)
In-Reply-To: <OF233D7062.48FA865C-ON4825806E.000544C5-4825806E.00093C07@zte.com.cn>
Hi Tang,
> As to process several uevents for the same physical devices, I think
> the opinions
> different between us is "FILTER" or "MERGER". Personally, I think
> Merger is more
> accuracy, for example, we receive 4 paths addition uevent messages
> from the same
> physical devices:
> 1)uevent add sdb
> 2)uevent add sdc
> 3)uevent add sdd
> 4)uevent add sde
>
> We cannot just filter the 1)2)3) uevent messages but only process the
> 4)uevent message,
> which would cause losing paths of this multipath devices.
Of course. My "filtering" idea was meant for cases where several events
for the same device are queued, e.g.
1) add sda
2) change sda
3) delete sda
Is it always sufficient to look only at the last event in such a case?
I think so, but I'm not 100% certain.
Regards
Martin
--
dm-devel mailing list
dm-devel@redhat.com
https://www.redhat.com/mailman/listinfo/dm-devel
next prev parent reply other threads:[~2016-11-17 10:48 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 [this message]
2016-11-18 1:02 ` tang.junhui
2016-11-18 7:39 ` Martin Wilck
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=1479379712.14706.23.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 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).