From: Ira Weiny <weiny2-i2BcT+NCU+M@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Jason Gunthorpe
<jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>,
Hal Rosenstock
<hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
"linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Sasha Khapyorsky <sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org>
Subject: Re: ib mad definitions
Date: Tue, 19 Oct 2010 18:12:56 -0700 [thread overview]
Message-ID: <20101019181256.d0a15afe.weiny2@llnl.gov> (raw)
In-Reply-To: <CF9C39F99A89134C9CF9C4CCB68B8DDF25B801F393-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On Tue, 19 Oct 2010 18:00:51 -0700
"Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:
> > Can we at least agree on the usage of these structures first? Are the
> > constants going to be in host or network byte order?
>
> I was simply suggesting to 'move' some of the existing structures and defines.
>
> > Are you going to make something like the kernel where there is a
> > native structure and pack/unpack function set?
>
> This would not be my preference.
>
> > Something macro-based like foo = GET_MEMBER(*pr,preference)
> >
> > Network byte order casting structures?
> >
> > Host byte order casting structures? (my favorite)
> >
> > bitfields?
>
> again - not my preference
>
> > Ira, I think the cleanest answer is that OSM keeps its type file, and
> > umad gets a new one that is cleaner, more capable and probably
> > incompatible. I'd hate to see us stick to the OSM scheme for umad just
> > for code compatability.
>
> Whatever is done must fit within the windows development framework that we use.
I am all for "cleaner, more capable..." but why incompatible? If we want to
start fresh and then convert OpenSM later, fine. But _don't_ forget to go
back and convert OpenSM, because if you leave ib_types.h out there someone is
going to use it and we are back to where we started... :-( Same for ibmad,
when these definitions become available in umad, mad can be simplified.
What I would like right now is to get the definitions in 1 place!
Right now there are 3 headers I find path record in.
libibverbs: sa.h
libibmad: mad.h
opensm: ib_types.h
Node type is defined in:
libibverbs: verbs.h
opensm: ib_types.h
libibmad: mad.h
I could go on.
What Sean is offering to do is move ib_types to umad. From there I can use
those definitions in mad (thus removing them from mad and consolidating at
least 2 of the 3 above). Perhaps use them in ibverbs as well? As a first
step I think we should take Sean up on his offer to start cleaning things up.
But we have to remove stuff as we go or we will just be defining yet another
place to look for these. After this we can look at making things cleaner
(perhaps even combining mad and umad, and including some of the ideas you have
above). As Sean said in another email, after this change; including
"ib_types.h" will be the same for anyone using it. The exception is that we
have simplified the code. I think this is a win-win with minimal work.
Ira
--
Ira Weiny
Math Programmer/Computer Scientist
Lawrence Livermore National Lab
925-423-8008
weiny2-i2BcT+NCU+M@public.gmane.org
--
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:[~2010-10-20 1:12 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-18 22:24 ib mad definitions Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25B7FB38D9-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-10-19 14:53 ` Mike Heinz
2010-10-19 15:14 ` Hal Rosenstock
[not found] ` <AANLkTimc7sgmyTvW_dgXarUvGzHcN3sRJ6TJQGxU5p7G-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-10-19 15:28 ` Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25B7FB3CDB-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-10-19 15:43 ` Hal Rosenstock
[not found] ` <AANLkTimbmQS0pcfF3CdSokPbAtbCZT7KFbWcSSNsYobk-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-10-19 16:48 ` Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25B7FB3E34-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-10-19 17:00 ` Hal Rosenstock
2010-10-19 17:22 ` Ira Weiny
[not found] ` <20101019102244.21cd2b1e.weiny2-i2BcT+NCU+M@public.gmane.org>
2010-10-19 18:50 ` Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25B7FB404C-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-10-19 20:45 ` Ira Weiny
[not found] ` <20101019134513.661470a8.weiny2-i2BcT+NCU+M@public.gmane.org>
2010-10-19 23:26 ` Smith, Stan
[not found] ` <3F6F638B8D880340AB536D29CD4C1E1925B937603F-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-10-19 23:44 ` Hefty, Sean
2010-10-19 21:29 ` Jason Gunthorpe
[not found] ` <20101019212926.GH10362-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-10-20 1:00 ` Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25B801F393-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-10-20 1:09 ` Jason Gunthorpe
[not found] ` <20101020010958.GA413-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-10-20 1:32 ` Ira Weiny
[not found] ` <20101019183257.3f609c45.weiny2-i2BcT+NCU+M@public.gmane.org>
2010-10-20 3:07 ` Jason Gunthorpe
2010-10-20 1:12 ` Ira Weiny [this message]
[not found] ` <20101019181256.d0a15afe.weiny2-i2BcT+NCU+M@public.gmane.org>
2010-10-20 3:28 ` Jason Gunthorpe
[not found] ` <20101020032818.GC413-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2010-10-20 16:06 ` Hefty, Sean
[not found] ` <CF9C39F99A89134C9CF9C4CCB68B8DDF25B801F651-osO9UTpF0USkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2010-10-20 17:28 ` Jason Gunthorpe
2010-10-20 17:10 ` Ira Weiny
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=20101019181256.d0a15afe.weiny2@llnl.gov \
--to=weiny2-i2bct+ncu+m@public.gmane.org \
--cc=hal.rosenstock-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=jgunthorpe-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=sashak-smomgflXvOZWk0Htik3J/w@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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