From: Eli Cohen <eli-LDSdmyG8hGV8YrgS2mwiifqBs+8SCbDb@public.gmane.org>
To: Sean Hefty <sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: 'Eli Cohen' <eli-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org>,
Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>,
Linux RDMA list
<linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: [PATCHv7 7/9] ib_core: Add API to support RoCEE from userspace
Date: Sun, 17 Jan 2010 10:13:47 +0200 [thread overview]
Message-ID: <20100117081347.GA30297@mtls03> (raw)
In-Reply-To: <52D379D24301435CB26E9B1FE51DBA57-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
On Wed, Jan 13, 2010 at 01:55:41PM -0800, Sean Hefty wrote:
> >Add ib_uverbs_get_mac() to be used by ibv_create_ah() to retirieve the remote
> >port's MAC address from the remote port's GID. Port link layer is also returned
> >by ibv_query_port().
>
> Is this really to map the GID of a remote port to its MAC address, or is the
> mapping for a local port?
>
> If it's the former, then I would expect the functionality to more naturally fall
> into ib_addr, with rdma_resolve_addr being the user space interface for this.
Actually the intention is that this API will resolve any GID, local
or remote, to the port's MAC address. I am not sure if
rdma_resolve_addr() is a good choice for this task since it involves
sockets stuff; and if we want to utilize this API for pure IB verbs
then that would be inappropriate.
>
> >+/**
> >+ * ib_get_mac - get the mac address for the specified gid
> >+ * @device: IB device used for traffic
> >+ * @port: port number used.
> >+ * @gid: gid to be resolved into mac
> >+ * @mac: mac of the port bearing this gid
> >+ */
> >+int ib_get_mac(struct ib_device *device, u8 port, u8 *gid, u8 *mac);
>
> Other calls use union ib_gid * where gids are expected.
Agree. Will change this.
--
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-01-17 8:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 10:33 [PATCHv7 7/9] ib_core: Add API to support RoCEE from userspace Eli Cohen
2010-01-13 21:55 ` Sean Hefty
[not found] ` <52D379D24301435CB26E9B1FE51DBA57-Zpru7NauK7drdx17CPfAsdBPR1lH4CV8@public.gmane.org>
2010-01-17 8:13 ` Eli Cohen [this message]
2010-01-18 7:53 ` Or Gerlitz
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=20100117081347.GA30297@mtls03 \
--to=eli-ldsdmyg8hgv8yrgs2mwiifqbs+8scbdb@public.gmane.org \
--cc=eli-VPRAkNaXOzVS1MOuV/RT9w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=rdreier-FYB4Gu1CFyUAvxtiuMwx3w@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