From: "David Harton (dharton)" <dharton@cisco.com>
To: Louis Luo <llouis@vmware.com>, Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Yong Wang <yongwang@vmware.com>
Subject: Re: [dpdk-dev] vmxnet3 Maintainer?
Date: Thu, 3 May 2018 10:58:40 +0000 [thread overview]
Message-ID: <43159ac7110c422ba54c024078c37af0@XCH-RCD-016.cisco.com> (raw)
In-Reply-To: <61DEE715-919A-4E79-9766-269C55869900@vmware.com>
Excellent!
I unicasted Yong earlier when I saw the ACKs to vmxnet3 patches. I'll add you there.
Thanks Louis,
Dave
> -----Original Message-----
> From: Louis Luo <llouis@vmware.com>
> Sent: Wednesday, May 02, 2018 5:55 PM
> To: Thomas Monjalon <thomas@monjalon.net>; David Harton (dharton)
> <dharton@cisco.com>
> Cc: dev@dpdk.org; Yong Wang <yongwang@vmware.com>
> Subject: Re: [dpdk-dev] vmxnet3 Maintainer?
>
> Hi Dave,
>
> The previous maintainer, Shri, has left VMware. Now Yong is taking the
> maintainer's role and I will work on the vmxnet3 driver. I haven't heard
> from Shri about the issue before. We can setup a testbed to reproduce the
> issue. Can you describe your setup? The issue reported by Paul in the
> following link was from 2016 and the ESX version was pretty old. Which
> ESX/Linux/DPDK version do you use?
>
> Thanks,
> Louis
>
> On 5/2/18, 2:02 PM, "dev on behalf of Thomas Monjalon" <dev-
> bounces@dpdk.org on behalf of thomas@monjalon.net> wrote:
>
> 02/05/2018 22:38, David Harton (dharton):
> > I've encountered a couple scenarios with vmxnet3 (dpdk 2.2 and
> 16.07) that look pretty much identical to this:
> > https://urldefense.proofpoint.com/v2/url?u=http-
> 3A__dpdk.org_ml_archives_users_2016-
> 2DOctober_001063.html&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ&r=y25HyFjCYzilk6V6
> ZP1fv_ZqnUERYZnHOMXviGNhdyQ&m=b0fOlYK3AC8HKUkrELsQZXwDfRGxc44mixhpABK56JM&
> s=pcQXE-BzpV_QVQbRgScrJzo9wpcFcmAYpJ_xN10qOmM&e=
> >
> > Do we have a maintainer for the vmxnet3 driver? I tried emailing
> the one listing in the MAINTAINERS file but the mail bounced.
>
> The maintainer changed recently.
> It is Yong Wang <yongwang@vmware.com> (Cc'ed).
>
> > Is anyone familiar with the issue described in the thread above?
>
>
>
>
>
>
prev parent reply other threads:[~2018-05-03 10:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 20:38 David Harton (dharton)
2018-05-02 21:02 ` Thomas Monjalon
2018-05-02 21:54 ` Louis Luo
2018-05-03 10:58 ` David Harton (dharton) [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=43159ac7110c422ba54c024078c37af0@XCH-RCD-016.cisco.com \
--to=dharton@cisco.com \
--cc=dev@dpdk.org \
--cc=llouis@vmware.com \
--cc=thomas@monjalon.net \
--cc=yongwang@vmware.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).