From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas.monjalon@6wind.com>
Received: from mail-wi0-f173.google.com (mail-wi0-f173.google.com
 [209.85.212.173]) by dpdk.org (Postfix) with ESMTP id EC5B87FF2
 for <dev@dpdk.org>; Mon, 27 Oct 2014 14:37:47 +0100 (CET)
Received: by mail-wi0-f173.google.com with SMTP id ex7so6416932wid.6
 for <dev@dpdk.org>; Mon, 27 Oct 2014 06:46:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:from:to:cc:subject:date:message-id:organization
 :user-agent:in-reply-to:references:mime-version
 :content-transfer-encoding:content-type;
 bh=Xl53f7RkEzZacojqc1+y579xpxgrn9bjl1L+x/REcrc=;
 b=PNcnh43xvcMPuR8P1M1RIjWr90+jXjwXs2hTjwvrbDTT8TlARS709yus5Rnpb83+vc
 Y88HnEQoix6754IWqdTu5BWT8VfLnt2jXwj1vUzorqnZwvS24QFmyASjI4HTs2PISjXz
 olK2HS2Ee19UGlCyvlbqGgb51ubao2/55X6pA7U8T9iT3Xas6te9jXgb8+lgKfkQ1E8q
 PKpXrambUntYklOqxdU6yu9V5lyEhUZS1XuvEk5ErxfOhZrbJeF9gusxr6fHMD2KbqPI
 dIaG/OKAOb5OMrvLNjg4wfmda/l0g+4odtWk6W5c9+O6nbWEdrTNNMiWa717VgGoBBH3
 ligw==
X-Gm-Message-State: ALoCoQllE6IxpI9AR4CpfeYwcVbNHRHZ9xXz2OUBxmy32zalpxgs3L4dXMfo62e2JdR6XSO1blCp
X-Received: by 10.180.212.48 with SMTP id nh16mr21458586wic.50.1414417590556; 
 Mon, 27 Oct 2014 06:46:30 -0700 (PDT)
Received: from xps13.localnet (136-92-190-109.dsl.ovh.fr. [109.190.92.136])
 by mx.google.com with ESMTPSA id lm9sm15647314wjc.45.2014.10.27.06.46.29
 for <multiple recipients>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Mon, 27 Oct 2014 06:46:29 -0700 (PDT)
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Liu, Jijiang" <jijiang.liu@intel.com>
Date: Mon, 27 Oct 2014 14:46:13 +0100
Message-ID: <2858055.qKaWYEhIlQ@xps13>
Organization: 6WIND
User-Agent: KMail/4.14.2 (Linux/3.17.1-1-ARCH; KDE/4.14.2; x86_64; ; )
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A7AB624@SHSMSX104.ccr.corp.intel.com>
References: <1414376006-31402-1-git-send-email-jijiang.liu@intel.com>
 <F35DEAC7BCE34641BA9FAC6BCA4A12E70A7AB624@SHSMSX104.ccr.corp.intel.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v8 00/10] Support VxLAN on Fortville
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Oct 2014 13:37:48 -0000

2014-10-27 02:41, Zhang, Helin:
> > The patch set supports VxLAN on Fortville based on latest rte_mbuf structure.
> > 
> > It includes:
> >  - Support VxLAN packet identification by configuring UDP tunneling port.
> >  - Support VxLAN packet filters. It uses MAC and VLAN to point
> >    to a queue. The filter types supported are listed below:
> >    1. Inner MAC and Inner VLAN ID
> >    2. Inner MAC address, inner VLAN ID and tenant ID.
> >    3. Inner MAC and tenant ID
> >    4. Inner MAC address
> >    5. Outer MAC address, tenant ID and inner MAC
> >  - Support VxLAN TX checksum offload, which include outer L3(IP), inner L3(IP)
> > and inner L4(UDP,TCP and SCTP)
> > 
> > Change notes:
> > 
> >  v8)  * Fix the issue of redundant "PKT_RX" and the comma missing in the
> > pkt_rx_flag_names[] in the rxonly.c file.
> > 
> > Jijiang Liu (10):
> >   change rte_mbuf structures
> >   add data structures of UDP tunneling
> >   add VxLAN packet identification API in librte_ether
> >   support VxLAN packet identification in i40e
> >   test VxLAN packet identification in testpmd.
> >   add data structures of tunneling filter in rte_eth_ctrl.h
> >   implement the API of VxLAN packet filter in i40e
> >   test VxLAN packet filter
> >   support VxLAN Tx checksum offload in i40e
> >   test VxLAN Tx checksum offload
> 
> Acked-by: Helin Zhang <helin.zhang@intel.com>

Applied

I fixed logs which had \n despite recent log rework.
I think there is also a wording error: you are writing VxLAN with x lowercase
but standard is writing it all uppercase: VXLAN. Do you agree?

Thanks
-- 
Thomas