From: Haggai Eran <haggaie-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
To: Wenda Ni <wonda.ni-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Kamal Heib <kamalh-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
Subject: Re: SoftRoCE V1
Date: Thu, 31 Dec 2015 10:48:29 +0200 [thread overview]
Message-ID: <5684EBDD.8070204@mellanox.com> (raw)
In-Reply-To: <CAEnvTt1KBHXYzjfHKmWkQtUs1J-ABhY_maQibR5LE9t+F25sYQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On 29/12/2015 18:01, Wenda Ni wrote:
> Hi experts,
>
> We have several Mellanox RoCE V1 NIC cards, and would like to try
> communicating with SoftRoCE V1.
>
> We are using branch rxe-3.0 from https://github.com/SoftRoCE/rxe-dev
> according to the Soft-RoCE README Rev 1.0 issued from Mellanox last
> year.
>
>
> Testing using pingpong examples from libibverbs (hardware RoCE <->
> SoftRoCE) already shows a bug in Ethernet CRC generation. We expect
> further bugs along the way.
>
> So we would like to know for SoftRoCE V1, are we using the latest
> branch? Also, is it still tied to SLES11 SP3 OS?
Kamal can correct me if I'm wrong, but I think the updated branch is rxe_submission-v2.
However it doesn't support RoCE v1, only RoCE v2.
> There are very few documentations we can find, so we hope this is the
> right place to ask such questions.
I can't think of a better place.
Regards,
Haggai
--
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:[~2015-12-31 8:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-29 16:01 SoftRoCE V1 Wenda Ni
[not found] ` <CAEnvTt1KBHXYzjfHKmWkQtUs1J-ABhY_maQibR5LE9t+F25sYQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-12-31 8:48 ` Haggai Eran [this message]
[not found] ` <5684EBDD.8070204-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2015-12-31 9:04 ` Kamal Heib
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=5684EBDD.8070204@mellanox.com \
--to=haggaie-vpraknaxozvwk0htik3j/w@public.gmane.org \
--cc=kamalh-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wonda.ni-Re5JQEeQqe8AvxtiuMwx3w@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