From: Hal Rosenstock <hal-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: "Hefty, Sean" <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Roland Dreier <roland-BHEL68pLQRGGvPXPguhicg@public.gmane.org>,
David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
"linux-rdma
(linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org)"
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
"netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCH 1/25 v2] rdma/cm: define native IB address
Date: Thu, 31 May 2012 11:53:51 -0400 [thread overview]
Message-ID: <4FC7940F.5010309@dev.mellanox.co.il> (raw)
In-Reply-To: <1828884A29C6694DAF28B7E6B8A823733B7669D7-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
On 3/7/2012 12:45 PM, Hefty, Sean wrote:
>> On Mon, Feb 27, 2012 at 2:22 PM, Hefty, Sean <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> wrote:
>>>>> --- a/include/linux/socket.h
>>>>> +++ b/include/linux/socket.h
>>>>> @@ -184,6 +184,7 @@ struct ucred {
>>>>> #define AF_PPPOX 24 /* PPPoX sockets */
>>>>> #define AF_WANPIPE 25 /* Wanpipe API Sockets */
>>>>> #define AF_LLC 26 /* Linux LLC */
>>>>> +#define AF_IB 27 /* Native InfiniBand address */
>>>>> #define AF_CAN 29 /* Controller Area Network */
>>>>> #define AF_TIPC 30 /* TIPC
>> sockets */
>>>>> #define AF_BLUETOOTH 31 /* Bluetooth sockets */
>>>>> @@ -227,6 +228,7 @@ struct ucred {
>>>>> #define PF_PPPOX AF_PPPOX
>>>>> #define PF_WANPIPE AF_WANPIPE
>>>>> #define PF_LLC AF_LLC
>>>>> +#define PF_IB AF_IB
>>>>> #define PF_CAN AF_CAN
>>>>> #define PF_TIPC AF_TIPC
>>>>> #define PF_BLUETOOTH AF_BLUETOOTH
>>>>
>>>> Has this been run by the networking community? Are they OK with this
>>>> assignment?
>>>
>>> I did copy netdev on the original submissions, but I don't remember any
>> explicit ack or nack.
>>
>> David, any feeling yay or nay about adding these?
>>
>> Is the kernel the final arbiter of AF_xxx / PF_xxx assignments, or
>> is there anything else we have to worry about?
>
> To clarify the intent of this change:
>
> The RDMA CM allows users to specify addresses using struct sockaddr. Today, only INET/6 are supported.
> The intent is to allow a user to specify native InfiniBand addresses through that interface.
> In the more immediate, this helps to solve InfiniBand scaling issues.
Yes, this is key for InfiniBand scaling.
> Longer term, this can also be used to control path failover.
This AF_IB patch series appears to be stalled unless I missed something
on the list. What needs to be done to revive it/move it along ?
Thanks.
-- Hal
>
> - Sean
> --
> 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
>
--
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
prev parent reply other threads:[~2012-05-31 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Acy/UbLfE8J2OYoiRYW93MzjgJGL8Q==>
2011-12-20 21:44 ` [PATCH 1/25 v2] rdma/cm: define native IB address Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A8237325661ADD-P5GAC/sN6hlcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-02-27 22:07 ` Roland Dreier
[not found] ` <CAL1RGDUu9sUbeWgBwivnAeXf+OWX_m5MRrizfzP4ni-FOGxiTQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-02-27 22:22 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A82373374F1A64-P5GAC/sN6hlcIJlls4ac1rfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-03-05 20:34 ` Roland Dreier
[not found] ` <CAL1RGDV-oYkNwQQUkAuUEHTH=HbmLk6Kv7JRnJ3XxN1DMNzLNQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-07 17:45 ` Hefty, Sean
[not found] ` <1828884A29C6694DAF28B7E6B8A823733B7669D7-P5GAC/sN6hmkrb+BlOpmy7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2012-05-31 15:53 ` Hal Rosenstock [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=4FC7940F.5010309@dev.mellanox.co.il \
--to=hal-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=roland-BHEL68pLQRGGvPXPguhicg@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 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.