DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Eduard Serra <eserra@vmware.com>
Cc: Eduard Serra <eduser25@gmail.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/vmxnet3: synchronize vmxnet definitionswith 6.7 public
Date: Sun, 07 Apr 2019 11:16:44 +0200	[thread overview]
Message-ID: <2803318.F4SQZn5iSM@xps> (raw)
Message-ID: <20190407091644.ocqZJnfXDbBm7WGCgNI_QiiMddgsDoUeLyf7SHmfTj4@z> (raw)
In-Reply-To: <5ca94617.1c69fb81.5593b.1f0d@mx.google.com>

07/04/2019 02:36, Eduard Serra:
> Hey Thomas,
> 
> Thanks for taking a look.
> My intentions is to port some of the new features on top of this patch (flow steering, ESP RSS – preparing the patches right now) which we are using inhouse to DPDK, however for that I require to upgrade definitions.
> The ownership of this definitions is VMware’s ESX team, my main goal was to keep the definitions identical to most recent ESX’s, for correctness and ease of maintenance later on, instead of just adding bits and pieces.

I understand, but still we need to have a good history of the changes
with some explanations of the "what" and "why".
Please communicate with the team authoring the changes to get
the explanations and do a proper split.

Thanks



  parent reply	other threads:[~2019-04-07  9:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-04 20:54 [dpdk-dev] [PATCH] net/vmxnet3: synchronize vmxnet definitions with " eduser25
2019-04-04 20:54 ` eduser25
2019-04-04 21:26 ` Thomas Monjalon
2019-04-04 21:26   ` Thomas Monjalon
2019-04-07  0:36   ` [dpdk-dev] [PATCH] net/vmxnet3: synchronize vmxnet definitionswith " Eduard Serra
2019-04-07  0:36     ` Eduard Serra
2019-04-07  9:16     ` Thomas Monjalon [this message]
2019-04-07  9:16       ` Thomas Monjalon

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=2803318.F4SQZn5iSM@xps \
    --to=thomas@monjalon.net \
    --cc=dev@dpdk.org \
    --cc=eduser25@gmail.com \
    --cc=eserra@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).