All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
To: sekharan@linux.vnet.ibm.com
Cc: dm-devel <dm-devel@redhat.com>
Subject: Re: rdac priority checker changing priorities
Date: Tue, 23 Jun 2009 08:20:49 +0200	[thread overview]
Message-ID: <4A407441.2060701@suse.de> (raw)
In-Reply-To: <1245718044.10657.12.camel@chandra-ubuntu>

Chandra Seetharaman wrote:
> Hi Hannes,
> 
> Please see the attached file for the real example.
> 
> Can I go ahead and generate a patch to increase the priority of the
> preferred path to say, 50 ?
> 
No. That's just wrong and we'll run into the same problem once
someone increases the number of paths to 50.

What we should do here is to modify the priority value, or
rather the way priority is used.

We should be splitting the current priority value into two
fields, pg priority and number of paths in a pg.
pg priority is the priority of a _single_ path here, and,
by definition as we're using group_by_prio, the priority
of each path in the pg.

Then we should be modifying the algorithm to choose the
next pg to do something like this:

-> Choose the pg with the highest priority
-> If two pgs have the same priority choose the pg
   with the highest path count. Maybe we could
   even use the highest _valid_ path count here,
   depending if we have the information at that point.

This algorithm would solve the problem we're having
now once and for all.

Just adding the priorities of the individual paths will
always lead to these type of problems.

I see if I can find some time to draw up a patch.

Cheers,

Hannes
-- 
Dr. Hannes Reinecke		      zSeries & Storage
hare@suse.de			      +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2009-06-23  6:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-29 22:34 rdac priority checker changing priorities Lucas Brasilino
2009-04-30  6:25 ` Hannes Reinecke
2009-04-30 18:05   ` Chandra Seetharaman
2009-05-04 10:43     ` Hannes Reinecke
2009-05-04 17:30       ` Chandra Seetharaman
2009-06-23  0:47       ` Chandra Seetharaman
2009-06-23  6:20         ` Hannes Reinecke [this message]
2009-05-05 17:59     ` Lucas Brasilino

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=4A407441.2060701@suse.de \
    --to=hare@suse.de \
    --cc=dm-devel@redhat.com \
    --cc=sekharan@linux.vnet.ibm.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.