From: christophe varoqui <christophe.varoqui@free.fr>
To: device-mapper development <dm-devel@redhat.com>
Cc: "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"linux-hotplug-devel@lists.sourceforge.net"
<linux-hotplug-devel@lists.sourceforge.net>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>
Subject: [ANNOUNCE] multipath-tools-0.3.4
Date: Sun, 24 Oct 2004 22:14:48 +0000 [thread overview]
Message-ID: <1098656088.9350.88.camel@zezette> (raw)
In-Reply-To: <1098269169.417641f18a234@imp1-q.free.fr>
Hello,
here goes multipath-tools-0.3.4
Many structural change, consequences of the Suse review.
Highlights are :
* glibc compilation, uses system libraries where possible
* multipath & multipathd now use the same path checkers.
Consequence being multipath now need sg loaded
* checkers now can return more than UP or DOWN and they take
2 more arguments :
* msg : to let the checker pass log mesg to the core
* context : a persistent data store the checkers can
use at discretion
* multipath pgpolicies rework : I broke the group_by_serial
LUN balancing. This is volontary : I'd like someone affected
to come up with a callout binary to do the balancing based on
the priority framework.
Full ChangeLog for the release :
* [multipathd] exec multipath precisely : pass in the path
or the devmap to update. No more full reconfiguration, and
really use the reinstate feature of multipath.
* [multipathd] check all paths, not only failed ones. Path
checker now trigger on state change (formerly triggred on
state = UP condition)
* [multipathd] incremental updatepaths() instead of scrap /
refresh all logic.
* [multipathd] path checkers now take *msg and *context
params. consensus w/ lmb at suse. tur.c modified as example
* [multipath] assemble maps in PG vector descending order to
fit the layered policies design
* [multipath] stop playing with strings in pgpolicies, as it
uses more memory and looses info for no gain
* [multipath] remove lk2.4 scsi ioctl scsi_type remnant
* [multipath] layered pgpolicies : (see pgpolicies.c)
* group_by_status
* group_by_serial | multibus | failover | group_by_prio
* sort_pg_by_summed_prio
thus remove duplicated failedpath logic in pgpolicies
* [checkers] framework for arbitrate checkers return values
* [multipathd] scrap yet another reinvented wheel in the
name of the LOG macro : learn the existance of setloglevel
and LOG_UPTO macro
* glibc make with "make BUILD=glibc", asked by lmb at suse
As usual, doc and download at :
http://christophe.varoqui.free.fr/
regards,
--
christophe varoqui <christophe.varoqui@free.fr>
-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2004-10-24 22:14 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-25 0:24 [ANNOUNCE] multipath-tools-0.2.9 christophe varoqui
2004-10-06 9:22 ` [ANNOUNCE] multipath-tools-0.3.0 christophe.varoqui
2004-10-06 9:50 ` [dm-devel] " Lars Marowsky-Bree
2004-10-06 10:18 ` christophe.varoqui
2004-10-11 12:00 ` Lars Marowsky-Bree
2004-10-11 12:31 ` christophe.varoqui
2004-10-07 20:01 ` Dave Olien
2004-10-08 12:49 ` christophe.varoqui
2004-10-11 11:50 ` [ANNOUNCE] multipath-tools-0.3.1 christophe.varoqui
2004-10-12 18:35 ` Dave Olien
2004-10-17 14:03 ` multipath-tools-0.3.2 christophe varoqui
2004-10-20 10:46 ` [ANNOUNCE] multipath-tools-0.3.3 christophe.varoqui
2004-10-24 22:14 ` christophe varoqui [this message]
2004-10-25 8:22 ` [ANNOUNCE] multipath-tools-0.3.4 Arjan van de Ven
2004-10-25 9:38 ` christophe.varoqui
2004-10-25 10:39 ` Douglas Gilbert
2004-10-25 21:03 ` [dm-devel] " Lars Marowsky-Bree
2004-10-26 17:52 ` Mike Christie
2004-10-26 10:06 ` [ANNOUNCE] multipath-tools-0.3.5 christophe.varoqui
2004-11-01 17:08 ` [ANNOUNCE] multipath-tools-0.3.6 christophe varoqui
2004-11-11 23:10 ` [ANNOUNCE] multipath-tools-0.3.7 christophe varoqui
2004-11-25 14:55 ` [ANNOUNCE] multipath-tools-0.3.8 christophe varoqui
2004-12-05 15:43 ` [ANNOUNCE] multipath-tools-0.3.9 christophe varoqui
2004-12-12 17:20 ` [ANNOUNCE] multipath-tools-0.4.0 christophe varoqui
2004-12-20 16:01 ` [ANNOUNCE] multipath-tools-0.4.1 christophe varoqui
2004-12-21 22:02 ` [dm-devel] " Caushik, Ramesh
2004-12-21 23:03 ` christophe varoqui
2004-12-21 23:19 ` christophe varoqui
2004-12-22 19:26 ` Caushik, Ramesh
2004-12-22 19:45 ` christophe varoqui
2004-12-22 21:05 ` James.Smart
2004-12-22 21:23 ` christophe varoqui
2004-12-22 21:54 ` Caushik, Ramesh
2004-12-23 13:28 ` Christoph Hellwig
2004-12-23 12:19 ` James.Smart
2005-01-23 23:03 ` [ANNOUNCE] multipath-tools-0.4.2 christophe varoqui
2005-03-19 14:27 ` [ANNOUNCE] multipath-tools-0.4.3 christophe varoqui
2005-04-24 22:26 ` [ANNOUNCE] multipath-tools-0.4.4 christophe varoqui
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=1098656088.9350.88.camel@zezette \
--to=christophe.varoqui@free.fr \
--cc=dm-devel@redhat.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-raid@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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).