From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Stephen Bates <sbates-pv7U853sEMVWk0Htik3J/w@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
monis-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org,
yonatanc-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Subject: Re: [PATCH v1] rdma_rxe: Ensure rdma_rxe init occurs at correct time
Date: Sat, 1 Oct 2016 19:03:40 -0400 [thread overview]
Message-ID: <ca8674c6-eb71-a076-36ee-dfd84a7b45cd@redhat.com> (raw)
In-Reply-To: <1474644731-27818-1-git-send-email-sbates-pv7U853sEMVWk0Htik3J/w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 806 bytes --]
On 9/23/2016 11:32 AM, Stephen Bates wrote:
> This patch is based off v4.8-rc6 with the recent rxe bugfix patchset
> applied [1].
>
> There is a problem when CONFIG_RDMA_RXE=y and CONFIG_IPV6=y. This
> results in the rdma_rxe initialization occurring before the IPv6
> services are ready. This patch delays the initialization of rdma_rxe
> until after the IPv6 services are ready. This fix is based on one
> proposed by Logan Gunthorpe on a much older code base [2].
>
> [1] http://marc.info/?l=linux-rdma&m=147307739626544&w=2
>
> [2] https://github.com/sbates130272/qemu-minimal/blob/rdma/patches/\
> 0001-Changes-needed-to-use-rxe-compiled-into-the-kernel.patch
Thanks, applied.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG Key ID: 0E572FDD
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 884 bytes --]
prev parent reply other threads:[~2016-10-01 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 15:32 [PATCH v1] rdma_rxe: Ensure rdma_rxe init occurs at correct time Stephen Bates
[not found] ` <1474644731-27818-1-git-send-email-sbates-pv7U853sEMVWk0Htik3J/w@public.gmane.org>
2016-10-01 23:03 ` Doug Ledford [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=ca8674c6-eb71-a076-36ee-dfd84a7b45cd@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=monis-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=sbates-pv7U853sEMVWk0Htik3J/w@public.gmane.org \
--cc=yonatanc-VPRAkNaXOzVWk0Htik3J/w@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