public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org>
Cc: Robert Woodruff
	<robert.j.woodruff-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
	"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Michael Heinz
	<michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org>,
	Openfabrics-ewg-0P3JtQMG0aQdnm+yROfE0A@public.gmane.org
Subject: Re: [PATCH] infiniband-diags/scripts/ibcheckerrs.in: emulate all ports if necessary.
Date: Fri, 7 May 2010 00:13:28 +0300	[thread overview]
Message-ID: <20100506211328.GI7099@me.iol.unh.edu> (raw)
In-Reply-To: <20100506091829.dd275edf.weiny2-i2BcT+NCU+M@public.gmane.org>

On 09:18 Thu 06 May     , Ira Weiny wrote:
> Upon thinking about this a bit more, and seeing Mikes patch.  I think that the
> patch which Mike sent some time ago is a better fix.  This will work fine for
> ibcheckerrs.  However ibcheckerrors will run AllPortSelect and then go on to
> query all the ports individually.  The patch below will cause a double read
> for each port which will kill ibcheckerrors performance on a large cluster.
> 
> Sasha, what is the status of Mikes patch?

Applied now.

Sasha
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2010-05-06 21:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06  2:47 [PATCH] infiniband-diags/scripts/ibcheckerrs.in: emulate all ports if necessary Ira Weiny
     [not found] ` <20100505194720.6f9d434c.weiny2-i2BcT+NCU+M@public.gmane.org>
2010-05-06 16:18   ` Ira Weiny
     [not found]     ` <20100506091829.dd275edf.weiny2-i2BcT+NCU+M@public.gmane.org>
2010-05-06 21:13       ` Sasha Khapyorsky [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=20100506211328.GI7099@me.iol.unh.edu \
    --to=sashak-smomgflxvozwk0htik3j/w@public.gmane.org \
    --cc=Openfabrics-ewg-0P3JtQMG0aQdnm+yROfE0A@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=michael.heinz-h88ZbnxC6KDQT0dZR+AlfA@public.gmane.org \
    --cc=robert.j.woodruff-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=weiny2-i2BcT+NCU+M@public.gmane.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