From: Thomas Monjalon <thomas@monjalon.net>
To: Stephen Hemminger <sthemmin@microsoft.com>
Cc: dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH] Revert "net/mlx: support IOVA VA mode"
Date: Mon, 22 Jul 2019 17:55:09 +0200 [thread overview]
Message-ID: <2082970.WY5cZRJGLO@xps> (raw)
In-Reply-To: <1951993.R3ThFuq71D@xps>
11/07/2019 00:18, Thomas Monjalon:
> 09/07/2019 16:39, Stephen Hemminger:
> > On Fri, 7 Jun 2019 16:08:41 -0700
> > Stephen Hemminger <stephen@networkplumber.org> wrote:
> >
> > > From: Stephen Hemminger <sthemmin@microsoft.com>
> > >
> > > This reverts commit 69c06d0e357ed0064b498d510d169603cf7308cd.
> > > That commit breaks support for netvsc PMD with MLX SRIOV
> > > on both Hyper-V and Azure.
> > >
> > > Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
> >
> > DPDK 19.08-rc is broken on Azure. This patch which seems to have been
> > ignored fixes it.
>
> This patch was not ignored. I was waiting for the IOVA changes
> to settle down. As a result, the revert will happen because the
> type RTE_KDRV_NIC_MLX is not needed anymore:
> https://patches.dpdk.org/patch/56314/
The revert is applied on master now.
> However, I don't understand how it is related to netvsc PMD.
> Please could you give more details?
Please did you investigate what happened?
prev parent reply other threads:[~2019-07-22 15:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-07 23:08 Stephen Hemminger
2019-06-12 21:39 ` Stephen Hemminger
2019-06-20 22:30 ` Stephen Hemminger
2019-07-09 14:39 ` Stephen Hemminger
2019-07-10 22:18 ` Thomas Monjalon
2019-07-22 15:55 ` Thomas Monjalon [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=2082970.WY5cZRJGLO@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=stephen@networkplumber.org \
--cc=sthemmin@microsoft.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).