All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
To: Al Chu <chu11-i2BcT+NCU+M@public.gmane.org>
Cc: "linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [infiniband-diags] [0/3] support --diff and --diffcheck in ibnetdiscover
Date: Wed, 14 Apr 2010 12:54:52 +0300	[thread overview]
Message-ID: <20100414095452.GQ10830@me> (raw)
In-Reply-To: <1271179075.17987.94.camel-X2zTWyBD0EhliZ7u+bvwcg@public.gmane.org>

On 10:17 Tue 13 Apr     , Al Chu wrote:
> 
> I had considered this at one point.  There were several reasons I
> decided to go w/ the cache idea.  Perhaps the major reason is that the
> current cache system has "all" the data (nodeinfo, portinfo, etc.)
> saved, whereas the normal ibnetdiscover output does not. So we would be
> limited in our diff output for what ibnetdiscover outputs (or perhaps
> limited in future extensions).  Adding a --diff into iblinkinfo is also
> on my list to do, but that wouldn't be possible w/ a cached text output
> (the cached text file doesn't store portinfo data).

That makes sense.

> This isn't to say there are downsides.  The major downside is that it's
> difficult to edit the cache when minor changes happen on the network
> (e.g. for our system administrators, when an HCA is replaced b/c a node
> dies). I have a tool for that (to be submitted soon too I hope :-).

It is difficult to edit and difficult to read. So I would really prefer
to have a text file (even with extended format). But well, let's see how
this will go.

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-04-14  9:54 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-07 17:05 [infiniband-diags] [0/3] support --diff and --diffcheck in ibnetdiscover Al Chu
     [not found] ` <1270659929.26381.38.camel-RLKWKRZIcZkVVsCFsIUZTRy+HRzXvqW9@public.gmane.org>
2010-04-13 13:08   ` Sasha Khapyorsky
2010-04-13 13:10     ` Sasha Khapyorsky
2010-04-13 17:17       ` Al Chu
     [not found]         ` <1271179075.17987.94.camel-X2zTWyBD0EhliZ7u+bvwcg@public.gmane.org>
2010-04-14  9:54           ` 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=20100414095452.GQ10830@me \
    --to=sashak-smomgflxvozwk0htik3j/w@public.gmane.org \
    --cc=chu11-i2BcT+NCU+M@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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 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.