From: Or Gerlitz <ogerlitz@mellanox.com>
To: sean.hefty@intel.com
Cc: linux-rdma@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v4 1/9] rdma/cm: define native IB address
Date: Wed, 13 Feb 2013 14:56:02 +0200 [thread overview]
Message-ID: <511B8D62.3050508@mellanox.com> (raw)
In-Reply-To: <1358891797-14625-2-git-send-email-sean.hefty@intel.com>
On 22/01/2013 23:56, sean.hefty@intel.com wrote:
> +
> +struct sockaddr_ib {
> + unsigned short int sib_family; /* AF_IB */
> + __be16 sib_pkey;
> + __be32 sib_flowinfo;
> + struct ib_addr sib_addr;
> + __be64 sib_sid;
> + __be64 sib_sid_mask;
> + __u64 sib_scope_id;
> +};
just a nit, maybe reorder the fields to better cope with their IPv6
buddies (where there is
such) from sockaddr_in6?
Also I see that both IPv6 header and IB GRH have a traffic class field
which is skipped in both
cases for the related sockaddr_ structure, not sure why, is this
something the kernel stack decides on and uses but not available for
applications to read/modify?
struct sockaddr_in6 {
unsigned short int sin6_family; /* AF_INET6 */
__be16 sin6_port; /* Transport layer port
# */
__be32 sin6_flowinfo; /* IPv6 flow information */
struct in6_addr sin6_addr; /* IPv6 address */
__u32 sin6_scope_id; /* scope id (new in
RFC2553) */
};
WARNING: multiple messages have this Message-ID (diff)
From: Or Gerlitz <ogerlitz@mellanox.com>
To: <sean.hefty@intel.com>
Cc: <linux-rdma@vger.kernel.org>, <netdev@vger.kernel.org>
Subject: Re: [PATCH v4 1/9] rdma/cm: define native IB address
Date: Wed, 13 Feb 2013 14:56:02 +0200 [thread overview]
Message-ID: <511B8D62.3050508@mellanox.com> (raw)
In-Reply-To: <1358891797-14625-2-git-send-email-sean.hefty@intel.com>
On 22/01/2013 23:56, sean.hefty@intel.com wrote:
> +
> +struct sockaddr_ib {
> + unsigned short int sib_family; /* AF_IB */
> + __be16 sib_pkey;
> + __be32 sib_flowinfo;
> + struct ib_addr sib_addr;
> + __be64 sib_sid;
> + __be64 sib_sid_mask;
> + __u64 sib_scope_id;
> +};
just a nit, maybe reorder the fields to better cope with their IPv6
buddies (where there is
such) from sockaddr_in6?
Also I see that both IPv6 header and IB GRH have a traffic class field
which is skipped in both
cases for the related sockaddr_ structure, not sure why, is this
something the kernel stack decides on and uses but not available for
applications to read/modify?
struct sockaddr_in6 {
unsigned short int sin6_family; /* AF_INET6 */
__be16 sin6_port; /* Transport layer port
# */
__be32 sin6_flowinfo; /* IPv6 flow information */
struct in6_addr sin6_addr; /* IPv6 address */
__u32 sin6_scope_id; /* scope id (new in
RFC2553) */
};
next prev parent reply other threads:[~2013-02-13 12:56 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 21:56 [PATCH v4 0/9] rdma/cm: Add support for native Infiniband addressing sean.hefty-ral2JQCrhuEAvxtiuMwx3w
[not found] ` <1358891797-14625-1-git-send-email-sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-01-22 21:56 ` [PATCH v4 1/9] rdma/cm: define native IB address sean.hefty-ral2JQCrhuEAvxtiuMwx3w
2013-02-11 18:02 ` Hefty, Sean
2013-02-13 12:51 ` Or Gerlitz
[not found] ` <1828884A29C6694DAF28B7E6B8A8237368B99D59-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-03-01 3:49 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A823736F35600F-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-03-06 15:40 ` Qperf and APM Suresh Shelvapille
[not found] ` <82EBBE0B04D4427381C29144BE078F2B-+IkoAhRkys/CbFgIbBqbbjGjJy/sRE9J@public.gmane.org>
2013-03-06 18:51 ` Luick, Dean
[not found] ` <4AF12E8016D2BF46BCDFCE8FAA77A3580394D479-96pTJSsuoYQd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-03-06 18:59 ` Suresh Shelvapille
[not found] ` <58D79FF01489431AB6D87CD4977F2E45-+IkoAhRkys/CbFgIbBqbbjGjJy/sRE9J@public.gmane.org>
2013-03-06 20:56 ` Luick, Dean
[not found] ` <4AF12E8016D2BF46BCDFCE8FAA77A3580394D4FB-96pTJSsuoYQd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-03-06 22:24 ` Suresh Shelvapille
[not found] ` <8AF67C8E913E4EE49D65CABA83E3DEBF-+IkoAhRkys/CbFgIbBqbbjGjJy/sRE9J@public.gmane.org>
2013-03-13 22:25 ` Luick, Dean
[not found] ` <4AF12E8016D2BF46BCDFCE8FAA77A3580394F46B-96pTJSsuoYQd3b2yrw5b5LfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-03-13 22:43 ` Suresh Shelvapille
2013-02-13 12:56 ` Or Gerlitz [this message]
2013-02-13 12:56 ` [PATCH v4 1/9] rdma/cm: define native IB address Or Gerlitz
2013-01-22 21:56 ` [PATCH v4 2/9] rdma/cm: Include AF_IB in loopback and any address checks sean.hefty-ral2JQCrhuEAvxtiuMwx3w
2013-01-22 21:56 ` [PATCH v4 4/9] rdma/cm: Update port reservation to support AF_IB sean.hefty-ral2JQCrhuEAvxtiuMwx3w
[not found] ` <1358891797-14625-5-git-send-email-sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-02-13 11:09 ` Or Gerlitz
2013-02-13 11:09 ` Or Gerlitz
[not found] ` <511B7474.3040201-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2013-02-13 17:44 ` Hefty, Sean
2013-02-13 18:10 ` Jason Gunthorpe
2013-02-13 18:19 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237368B9A432-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2013-02-13 18:26 ` Jason Gunthorpe
2013-02-13 18:37 ` Hefty, Sean
2013-01-22 21:56 ` [PATCH v4 6/9] rdma/cm: Do not modify sa_family when setting loopback address sean.hefty-ral2JQCrhuEAvxtiuMwx3w
2013-01-22 21:56 ` [PATCH v4 7/9] rdma/cm: Add helper functions to return id address information sean.hefty-ral2JQCrhuEAvxtiuMwx3w
2013-02-13 12:44 ` Or Gerlitz
2013-02-13 12:44 ` Or Gerlitz
2013-01-22 21:56 ` [PATCH v4 8/9] rdma/cm: Restrict AF_IB loopback to binding to IB devices only sean.hefty-ral2JQCrhuEAvxtiuMwx3w
2013-01-22 21:56 ` [PATCH v4 9/9] rdma/cm: Verify that source and dest sa_family are the same sean.hefty-ral2JQCrhuEAvxtiuMwx3w
2013-01-22 21:56 ` [PATCH v4 3/9] ib/addr: Add AF_IB support to ip_addr_size sean.hefty
2013-01-22 21:56 ` [PATCH v4 5/9] rdma/cm: Allow user to specify AF_IB when binding 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=511B8D62.3050508@mellanox.com \
--to=ogerlitz@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sean.hefty@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.