From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf1-f169.google.com (mail-pf1-f169.google.com [209.85.210.169]) by dpdk.org (Postfix) with ESMTP id B8B202B95 for ; Sun, 7 Apr 2019 02:36:41 +0200 (CEST) Received: by mail-pf1-f169.google.com with SMTP id y13so5407243pfm.11 for ; Sat, 06 Apr 2019 17:36:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:mime-version:to:cc:from:subject:date:importance :in-reply-to:references; bh=RRRJxoPsAxSrKGbi/LQ56jroNGkO2kbnvdtZgi+4V/s=; b=JDEdZHsPPsT23MkIPJC6jYtZ3EZeQFDAIV/t65co+bvtn0qKq9BjK1n5rQoLM+kZ5I yJtJNa2wtAs8OYCzCFQ0Bm8X4qCN8dQ+8IF0MXF2ZKqnGYs6daeZaiABh4Z/31BKsXY4 LRdLsSWDqxTZGuYeM8N3qTkOKV3guZ1wvpeDOBr+14DMCDevUsc6EpObDIciH1EzOlNR Wp2vzIeYTZ/wcF/Mee5wX9ASDUdzf3q4c01RPnanxWHrgjt8tIHGYus8IhvWAif2EvuL gwY+rkhtHDjhLLnRDRotUTlyThlxdlYlgROqHiAWIKvHKQaO7M3kDPvYQmugj52q6V1o 6MRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:mime-version:to:cc:from:subject:date :importance:in-reply-to:references; bh=RRRJxoPsAxSrKGbi/LQ56jroNGkO2kbnvdtZgi+4V/s=; b=rSaTMvCodoB61ZMBU2anRVesvEawn/V++nAg5+edBGhSLqEpnWSjCHwAqBp4EjxvCb PKN8hjLXlDFZNnX4R8b4w1B8IkbhJ1Hx8onO1Nf5T/9zfXdXcJhiCxf5UctHJULTZVAE SmqV0KyrMZPtN+5yYXiO0S5kQch9EABw+2nqFfrZG522j/KuYmeorGvfTB4Cuq/jOKXW srhx7KYtvC2jI5loQNXWPo5Ja//3C/tzs1amYsdDTLZe/6S89g2TjAKbr8VjHlPWidIG gHSb82+ldyXRZzG0Q6yHjVYJEeJTjqToWv2tNfI2I9/PRpDFsTeLOB+SoTQYwweCU2JC /b7g== X-Gm-Message-State: APjAAAWBPdK8VzAvz+1HpENqquZm4HaDPJXsXod+hCFAfJdXsJyX4Z46 9+oWGFbQCZMi19vDNNpwdi8= X-Google-Smtp-Source: APXvYqzC0IP1uam3BOrvdesEB84GvbA4DiF2bd60Ur+phubGkkeU4/1knJuNNcUFp6/LGzcX0mQhYA== X-Received: by 2002:a62:2a97:: with SMTP id q145mr21467231pfq.22.1554597400591; Sat, 06 Apr 2019 17:36:40 -0700 (PDT) Received: from ?IPv6:::ffff:192.168.2.111? (107-131-124-149.lightspeed.sntcca.sbcglobal.net. [107.131.124.149]) by smtp.gmail.com with ESMTPSA id q128sm33576534pga.60.2019.04.06.17.36.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Apr 2019 17:36:39 -0700 (PDT) Message-ID: <5ca94617.1c69fb81.5593b.1f0d@mx.google.com> MIME-Version: 1.0 To: Thomas Monjalon , Eduard Serra Cc: "dev@dpdk.org" From: Eduard Serra Date: Sat, 6 Apr 2019 17:36:41 -0700 Importance: normal X-Priority: 3 In-Reply-To: <1760571.o9aQio58az@xps> References: <1554411251-67227-1-git-send-email-eserra@vmware.com> <1760571.o9aQio58az@xps> Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [PATCH] net/vmxnet3: synchronize vmxnet definitionswith 6.7 public X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Apr 2019 00:36:42 -0000 Hey Thomas, Thanks for taking a look. My intentions is to port some of the new features on top of this patch (flo= w steering, ESP RSS =E2=80=93 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=E2=80=99s ESX team, my main goa= l was to keep the definitions identical to most recent ESX=E2=80=99s, for c= orrectness and ease of maintenance later on, instead of just adding bits an= d pieces. Does that sound good or should I follow a different approach? Thanks for the help, Edu PS. I mistakenly pushed this with private email address, I=E2=80=99ll chang= e to vmware=E2=80=99s domain one next iteration. From: Thomas Monjalon Sent: Thursday, April 4, 2019 2:26 PM To: Eduard Serra Cc: dev@dpdk.org; eduser25@gmail.com; yongwang@vmware.com Subject: Re: [dpdk-dev] [PATCH] net/vmxnet3: synchronize vmxnet definitions= with 6.7 public Hi, > From: Eduard Serra >=20 > Synchronize new definitions made public defs on ESX 6.7, which > include support for variety of new features and fixes on vmxnet3 > driver. Please, would it be possible to split this patch, and add explanations in each patch for each feature or cleanup? Thank you From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 0EC8DA0679 for ; Sun, 7 Apr 2019 02:36:46 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 048842E81; Sun, 7 Apr 2019 02:36:44 +0200 (CEST) Received: from mail-pf1-f169.google.com (mail-pf1-f169.google.com [209.85.210.169]) by dpdk.org (Postfix) with ESMTP id B8B202B95 for ; Sun, 7 Apr 2019 02:36:41 +0200 (CEST) Received: by mail-pf1-f169.google.com with SMTP id y13so5407243pfm.11 for ; Sat, 06 Apr 2019 17:36:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:mime-version:to:cc:from:subject:date:importance :in-reply-to:references; bh=RRRJxoPsAxSrKGbi/LQ56jroNGkO2kbnvdtZgi+4V/s=; b=JDEdZHsPPsT23MkIPJC6jYtZ3EZeQFDAIV/t65co+bvtn0qKq9BjK1n5rQoLM+kZ5I yJtJNa2wtAs8OYCzCFQ0Bm8X4qCN8dQ+8IF0MXF2ZKqnGYs6daeZaiABh4Z/31BKsXY4 LRdLsSWDqxTZGuYeM8N3qTkOKV3guZ1wvpeDOBr+14DMCDevUsc6EpObDIciH1EzOlNR Wp2vzIeYTZ/wcF/Mee5wX9ASDUdzf3q4c01RPnanxWHrgjt8tIHGYus8IhvWAif2EvuL gwY+rkhtHDjhLLnRDRotUTlyThlxdlYlgROqHiAWIKvHKQaO7M3kDPvYQmugj52q6V1o 6MRw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:mime-version:to:cc:from:subject:date :importance:in-reply-to:references; bh=RRRJxoPsAxSrKGbi/LQ56jroNGkO2kbnvdtZgi+4V/s=; b=rSaTMvCodoB61ZMBU2anRVesvEawn/V++nAg5+edBGhSLqEpnWSjCHwAqBp4EjxvCb PKN8hjLXlDFZNnX4R8b4w1B8IkbhJ1Hx8onO1Nf5T/9zfXdXcJhiCxf5UctHJULTZVAE SmqV0KyrMZPtN+5yYXiO0S5kQch9EABw+2nqFfrZG522j/KuYmeorGvfTB4Cuq/jOKXW srhx7KYtvC2jI5loQNXWPo5Ja//3C/tzs1amYsdDTLZe/6S89g2TjAKbr8VjHlPWidIG gHSb82+ldyXRZzG0Q6yHjVYJEeJTjqToWv2tNfI2I9/PRpDFsTeLOB+SoTQYwweCU2JC /b7g== X-Gm-Message-State: APjAAAWBPdK8VzAvz+1HpENqquZm4HaDPJXsXod+hCFAfJdXsJyX4Z46 9+oWGFbQCZMi19vDNNpwdi8= X-Google-Smtp-Source: APXvYqzC0IP1uam3BOrvdesEB84GvbA4DiF2bd60Ur+phubGkkeU4/1knJuNNcUFp6/LGzcX0mQhYA== X-Received: by 2002:a62:2a97:: with SMTP id q145mr21467231pfq.22.1554597400591; Sat, 06 Apr 2019 17:36:40 -0700 (PDT) Received: from ?IPv6:::ffff:192.168.2.111? (107-131-124-149.lightspeed.sntcca.sbcglobal.net. [107.131.124.149]) by smtp.gmail.com with ESMTPSA id q128sm33576534pga.60.2019.04.06.17.36.39 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 06 Apr 2019 17:36:39 -0700 (PDT) Message-ID: <5ca94617.1c69fb81.5593b.1f0d@mx.google.com> MIME-Version: 1.0 To: Thomas Monjalon , Eduard Serra Cc: "dev@dpdk.org" From: Eduard Serra Date: Sat, 6 Apr 2019 17:36:41 -0700 Importance: normal X-Priority: 3 In-Reply-To: <1760571.o9aQio58az@xps> References: <1554411251-67227-1-git-send-email-eserra@vmware.com> <1760571.o9aQio58az@xps> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] [PATCH] net/vmxnet3: synchronize vmxnet definitionswith 6.7 public X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190407003641.YKlRFo5SXOwA5k8O-vc21m_OhD9jh67rzKYT8L1Lgks@z> Hey Thomas, Thanks for taking a look. My intentions is to port some of the new features on top of this patch (flo= w steering, ESP RSS =E2=80=93 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=E2=80=99s ESX team, my main goa= l was to keep the definitions identical to most recent ESX=E2=80=99s, for c= orrectness and ease of maintenance later on, instead of just adding bits an= d pieces. Does that sound good or should I follow a different approach? Thanks for the help, Edu PS. I mistakenly pushed this with private email address, I=E2=80=99ll chang= e to vmware=E2=80=99s domain one next iteration. From: Thomas Monjalon Sent: Thursday, April 4, 2019 2:26 PM To: Eduard Serra Cc: dev@dpdk.org; eduser25@gmail.com; yongwang@vmware.com Subject: Re: [dpdk-dev] [PATCH] net/vmxnet3: synchronize vmxnet definitions= with 6.7 public Hi, > From: Eduard Serra >=20 > Synchronize new definitions made public defs on ESX 6.7, which > include support for variety of new features and fixes on vmxnet3 > driver. Please, would it be possible to split this patch, and add explanations in each patch for each feature or cleanup? Thank you