public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Yevgeny Kliteynik <kliteyn-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Cc: Linux RDMA <linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH] opensm/osm_vendor_mlx: fix compilation error
Date: Tue, 01 Dec 2009 23:42:14 +0200	[thread overview]
Message-ID: <4B158DB6.4020106@dev.mellanox.co.il> (raw)
In-Reply-To: <20091201163044.GV16607@me>

H5 Sasha,

Sasha Khapyorsky wrote:
> On 18:17 Tue 01 Dec     , Sasha Khapyorsky wrote:
>> On 16:45 Mon 30 Nov     , Yevgeny Kliteynik wrote:
>>> Fix compilation error of that was introduced with patch
>>> that added configurable transaction retries - osm_vendor_mlx
>>> didn't have a definition of OSM_DEFAULT_RETRY_COUNT.
> 
> BTW as far as I understand osm_vendor_mlx is used only with ibmgtsim.
> Right? If so could this be switched to osm_vendor_ibumad?
> 
> There is already libumad2sim.so (in ibsim) which catches all user_mad
> calls and redirects this to where you want. Adoption of such model to
> ibmgtsim would have a many advantages: it doesn't require OpenSM
> rebuild, it supports not only OpenSM and osmtest, but virtually any
> application which uses user_mad, it is really simple.
> 
> Finally this will leave us with only one vendor layer -
> osm_vendor_ibumad. (AFAIK windows OpenSM is moving this direction too).

That is the plan. It's not as trivial as it sounds.
Some things that exist in vendor_mlx do not exist
in vendor_ibumad (such as RMPP implementation), 
but this is certainly the plan. 

AFAIK, WinSM and ibmgtsim are the only two things 
that are using non-umad vendor. Once they both will
switch to umad, the whole vendor layers as it exists
today in OpenSM won't be necessary.

--Yevgeny 
 
> 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

      reply	other threads:[~2009-12-01 21:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-30 14:45 [PATCH] opensm/osm_vendor_mlx: fix compilation error Yevgeny Kliteynik
     [not found] ` <4B13DA83.4070400-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
2009-12-01 16:17   ` Sasha Khapyorsky
2009-12-01 16:30     ` Sasha Khapyorsky
2009-12-01 21:42       ` Yevgeny Kliteynik [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=4B158DB6.4020106@dev.mellanox.co.il \
    --to=kliteyn-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
    --cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=sashak-smomgflXvOZWk0Htik3J/w@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