From: Benjamin Marzinski <bmarzins@redhat.com>
To: Martin Wilck <mwilck@suse.com>
Cc: dm-devel@redhat.com, Xose Vazquez Perez <xose.vazquez@gmail.com>
Subject: Re: [PATCH v2 0/9] speeding up mpathpersist
Date: Wed, 29 May 2019 14:30:45 -0500 [thread overview]
Message-ID: <20190529193045.GF7630@octiron.msp.redhat.com> (raw)
In-Reply-To: <20190527125942.8366-1-mwilck@suse.com>
On Mon, May 27, 2019 at 02:59:33PM +0200, Martin Wilck wrote:
> We've had reports that mpathpersist doesn't scale well in environments
> with lots of IO devices. This patch set tries to address this problem
> with a few optimizations:
>
> - instead of doing a full path discovery at startup, only look at
> paths that are part of the maps being worked on
> - allow multiple PR commands in a single run using "batch files",
> without re-discovering everything between PR commands
> - avoid looking at priorities
>
> I've done some basic testing and it seems to work. It remains to be
> seen what the effect on performance really is, but the amount of system
> calls to be performed for a given set of mpathpersist actions should
> be substantially reduced in any case, especially when using batching.
>
> ---
> v2:
> - avoid memory leak with --batch-file (Ben Marzinski)
> - add documentation to usage() output and mpathpersist man page
> - integrate "mpathpersist.8: fix examples in man page" which I'd sent
> separately before
>
ACK for the set.
-Ben
>
> Martin Wilck (9):
> mpathpersist: call usage() just once on return
> mpathpersist: add option --batch-file (-f)
> mpathpersist: no need to treat error close() as fatal
> libmpathpersist: updatepaths: deal with missing pp->udev
> libmpathpersist: factor out initialization and teardown
> mpathpersist: initialize data structures only once
> libmpathpersist: don't bother with priorities
> mpathpersist.8: fix examples in man page
> mpathpersist.8: add documentation for --batch-file (-f)
>
> libmpathpersist/mpath_persist.c | 250 +++++++++++++++-----------------
> libmpathpersist/mpath_persist.h | 40 +++++
> mpathpersist/main.c | 227 ++++++++++++++++++++++-------
> mpathpersist/main.h | 1 +
> mpathpersist/mpathpersist.8 | 121 ++++++++++++++--
> 5 files changed, 440 insertions(+), 199 deletions(-)
>
> --
> 2.21.0
prev parent reply other threads:[~2019-05-29 19:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 12:59 [PATCH v2 0/9] speeding up mpathpersist Martin Wilck
2019-05-27 12:59 ` [PATCH v2 1/9] mpathpersist: call usage() just once on return Martin Wilck
2019-05-27 12:59 ` [PATCH v2 2/9] mpathpersist: add option --batch-file (-f) Martin Wilck
2019-05-27 12:59 ` [PATCH v2 3/9] mpathpersist: no need to treat error close() as fatal Martin Wilck
2019-05-27 12:59 ` [PATCH v2 4/9] libmpathpersist: updatepaths: deal with missing pp->udev Martin Wilck
2019-05-27 12:59 ` [PATCH v2 5/9] libmpathpersist: factor out initialization and teardown Martin Wilck
2019-05-27 12:59 ` [PATCH v2 6/9] mpathpersist: initialize data structures only once Martin Wilck
2019-05-27 12:59 ` [PATCH v2 7/9] libmpathpersist: don't bother with priorities Martin Wilck
2019-05-27 12:59 ` [PATCH v2 8/9] mpathpersist.8: fix examples in man page Martin Wilck
2019-05-27 12:59 ` [PATCH v2 9/9] mpathpersist.8: add documentation for --batch-file (-f) Martin Wilck
2019-05-29 19:30 ` Benjamin Marzinski [this message]
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=20190529193045.GF7630@octiron.msp.redhat.com \
--to=bmarzins@redhat.com \
--cc=dm-devel@redhat.com \
--cc=mwilck@suse.com \
--cc=xose.vazquez@gmail.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.