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
Subject: Re: [infiniband-diags] [PATCH] [2/2] split out scan specific data from ibnd_node_t
Date: Fri, 13 Nov 2009 00:31:42 +0200 [thread overview]
Message-ID: <20091112223142.GZ7192@me> (raw)
In-Reply-To: <1258048268.31785.185.camel-X2zTWyBD0EhliZ7u+bvwcg@public.gmane.org>
Hi Al,
On 09:51 Thu 12 Nov , Al Chu wrote:
>
> > Really? I thought that it could be a useful data for "advanced" uses.
>
> It was removed in commit 094f922a34d6378d6a3bd1d137f90d6530685f94. It
> was a simpler version of a patch that Ira had proposed on the mailing
> list.
This means that I'm applying patches too quickly :)
Then 'dest' is likely useless without such array, but 'portid' is not.
> > I cannot understand why are you trying to make things there as
> > "private" as technically possible (even on price of extra code size
> > and complexity). Finally it is an open source stuff, so let to users
> > to use it how they want and for their own responsibility. :)
>
> At the core of this patch (as well as some other patches I've submitted
> on libibnetdiscover before), is cleaning up the interface of
> libibnetdisc to be just the "core" of libibnetdisc. We could stick
> anything into the public structs that could have potential usefulness,
> but at some point I think we need to limit ourselves to only the core
> stuff. Why not add the ibmad_port to the structs? Or instead of
> putting just the guids or lids in the structs, why not also the pkeys,
> capability masks, or VL tables?
This can be done (if needed), but will require some efforts, and this is
not what I'm asking for. I'm just proposing to not remove potentially
useful things, that is all and this is for no price.
And cleaning interface is a good thing.
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
next prev parent reply other threads:[~2009-11-12 22:31 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-02 19:33 [infiniband-diags] [PATCH] [2/2] split out scan specific data from ibnd_node_t Al Chu
[not found] ` <1257190401.580.31.camel-X2zTWyBD0EhliZ7u+bvwcg@public.gmane.org>
2009-11-02 21:11 ` Al Chu
[not found] ` <1257196316.580.33.camel-X2zTWyBD0EhliZ7u+bvwcg@public.gmane.org>
2009-11-06 18:16 ` Sasha Khapyorsky
2009-11-06 18:34 ` Al Chu
[not found] ` <1257532494.18550.89.camel-X2zTWyBD0EhliZ7u+bvwcg@public.gmane.org>
2009-11-12 16:31 ` Sasha Khapyorsky
2009-11-12 17:51 ` Al Chu
[not found] ` <1258048268.31785.185.camel-X2zTWyBD0EhliZ7u+bvwcg@public.gmane.org>
2009-11-12 22:31 ` Sasha Khapyorsky [this message]
2009-11-13 17:50 ` Al Chu
2009-11-12 18:59 ` Ira Weiny
[not found] ` <20091112105930.4248e521.weiny2-i2BcT+NCU+M@public.gmane.org>
2009-11-12 22:59 ` Sasha Khapyorsky
2009-11-12 23:10 ` Sean Hefty
[not found] ` <E5EA56B85CF4411FA73984A608918052-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2009-11-13 2:09 ` Sasha Khapyorsky
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=20091112223142.GZ7192@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox