From: Sean Hefty <mshefty@ichips.intel.com>
To: Roland Dreier <rdreier@cisco.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
openib-general@openib.org
Subject: Re: Re: [PATCH 6/6] IB: userspace support for RDMA connection manager
Date: Mon, 06 Mar 2006 13:42:13 -0800 [thread overview]
Message-ID: <440CACB5.2010609@ichips.intel.com> (raw)
In-Reply-To: <adaoe0j5kd6.fsf@cisco.com>
Roland Dreier wrote:
> > +struct rdma_ucm_query_route_resp {
> > + __u64 node_guid;
> > + struct ib_user_path_rec ib_route[2];
> > + struct sockaddr_in6 src_addr;
> > + struct sockaddr_in6 dst_addr;
> > + __u32 num_paths;
> > + __u8 port_num;
> > + __u8 reserved[3];
> > +};
>
> Is there a 32-bit/64-bit compatibility problem here? From a quick
> look, struct sockaddr_in6 is not 8-byte aligned.
Unless I miss counted, they should be aligned. ib_user_path_rec is defined near
the end of patch 1/6.
+struct ib_user_path_rec {
+ __u8 dgid[16];
+ __u8 sgid[16];
+ __be16 dlid;
+ __be16 slid;
+ __u32 raw_traffic;
+ __be32 flow_label;
+ __u32 reversible;
+ __u32 mtu;
+ __be16 pkey;
+ __u8 hop_limit;
+ __u8 traffic_class;
+ __u8 numb_path;
+ __u8 sl;
+ __u8 mtu_selector;
+ __u8 rate_selector;
+ __u8 rate;
+ __u8 packet_life_time_selector;
+ __u8 packet_life_time;
+ __u8 preference;
+};
- Sean
next prev parent reply other threads:[~2006-03-06 21:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ORSMSX4011XvpFVjCRG00000009@orsmsx401.amr.corp.intel.com>
2006-03-06 21:33 ` [PATCH 6/6] IB: userspace support for RDMA connection manager Roland Dreier
2006-03-06 21:42 ` Sean Hefty [this message]
2006-03-06 21:58 ` Roland Dreier
2006-03-06 22:28 ` David S. Miller
2006-03-06 22:32 ` Roland Dreier
2006-03-06 22:39 ` David S. Miller
2006-03-06 22:41 ` Roland Dreier
2006-03-06 22:50 ` David S. Miller
2006-03-06 23:40 ` Roland Dreier
2006-03-07 0:05 ` [openib-general] " Bryan O'Sullivan
2006-03-07 0:10 ` Roland Dreier
2006-03-07 0:26 ` David S. Miller
2006-03-06 21:35 ` Roland Dreier
2006-03-06 21:43 ` Sean Hefty
2006-03-06 23:41 ` [PATCH 6/6 v2] " Sean Hefty
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=440CACB5.2010609@ichips.intel.com \
--to=mshefty@ichips.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=openib-general@openib.org \
--cc=rdreier@cisco.com \
/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;
as well as URLs for NNTP newsgroup(s).