From: Roland Dreier <rdreier@cisco.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: linux-kernel@vger.kernel.org, openib-general@openib.org,
netdev@vger.kernel.org
Subject: Re: Re: [PATCH 6/6] IB: userspace support for RDMA connection manager
Date: Mon, 06 Mar 2006 14:32:28 -0800 [thread overview]
Message-ID: <aday7zn432b.fsf@cisco.com> (raw)
In-Reply-To: <20060306.142814.109285730.davem@davemloft.net> (David S. Miller's message of "Mon, 06 Mar 2006 14:28:14 -0800 (PST)")
David> Please make sure you check "x86_64 vs. x86", and then
David> something like "powerpc64 vs. powerpc32" or "sparc64
David> vs. sparc32", as those are the two different classes of ABI
David> layouts.
Yes, I tried ppc64 vs ppc and it still comes out the same.
Unfortunately I don't have any sparc handy to try.
The fundamental question seems to be whether things like
struct foo {
struct sockaddr_in6 src;
struct sockaddr_in6 dst;
};
and
struct bar {
struct sockaddr_in6 a;
__u32 b;
};
end up being packed, even though struct sockaddr_in6 is 28 bytes in
size. And as far as I can tell, they always do, I guess because the
individual fields of struct sockaddr_in6 are all <= 32 bits.
- R.
next prev parent reply other threads:[~2006-03-06 22:32 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
2006-03-06 21:58 ` Roland Dreier
2006-03-06 22:28 ` David S. Miller
2006-03-06 22:32 ` Roland Dreier [this message]
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=aday7zn432b.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=openib-general@openib.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;
as well as URLs for NNTP newsgroup(s).