From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qk0-f179.google.com (mail-qk0-f179.google.com [209.85.220.179]) by dpdk.org (Postfix) with ESMTP id 9E3BB58F6 for ; Mon, 17 Apr 2017 05:43:39 +0200 (CEST) Received: by mail-qk0-f179.google.com with SMTP id f133so97214487qke.2 for ; Sun, 16 Apr 2017 20:43:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cfTYrEKFI8GesoVoIX5SgjZYU7ZGHHyomEeeFegs+wg=; b=N7bP8FQdRPl6LvZ5PS8t2qgj9LZSctmXvl2qrrtkzm5sYuDWiWd8askUgQu0IJnQ+v rgbOjFlE+Jr9lHHAzlSnupPc2rG/SBaAOre/U/jYhCBRMXOxv0lMoBEpjk3SG5J1iWSL tkT3tD3qDqiNHGGC4Z1zohWgPgSp1JPzVdo0bxj6ge2CaKTSH5IMGrhJ0hoSRWQggjr+ cRnusz6/34TZceEinBOy7OENeeNnFEMora7lbQjo+oSnbt3dw/Pe1uK0EAjVutkVy539 6j3FkJjr6IcOROM2bS/QJjY3aK+BA6T2DtKogqtXFwhUWeBdagHgfK91kegn3zDm86xc i0vA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=cfTYrEKFI8GesoVoIX5SgjZYU7ZGHHyomEeeFegs+wg=; b=PRrHDQMIbkPplZGjlk7xr1AcyPJmGMNs+wJbaX7+ytPLT/U3m/8+Ji4h30tKSJtJFG uXwAKdODlmMgbarHsZq9/nRFHKPdfWSx90EdOrtfbGoMHjQ20AfyS9Sex0OEh+X8M3ns 0aGjzfCKnMajOXjVli9ALTb9pxoeHCpUeIoTlPMUAxyRQOCtd9gpgJKuF2HcysvGSuv7 JcxUkrLFxtJJ7axGlIlfuShdkvShUljv+xBgbg9A8i3txFN4ZEeriQD7f0HHBDXdsmnY MA0rvSi/sJ6PjCtwKRJmlBImZnLzo4TNTZjebankbrNQA0A9RgPpjRPXi058U29MNLHi 2fmg== X-Gm-Message-State: AN3rC/7cgelpFYOwx2DAue1m6+JtK+b2EcQgVZ01O998NhEQGSCq6ywR Jc5JNTCNNJ93JoUZI76OIyQwIKl/8g== X-Received: by 10.55.79.216 with SMTP id d207mr6445506qkb.298.1492400619018; Sun, 16 Apr 2017 20:43:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.12.158.38 with HTTP; Sun, 16 Apr 2017 20:43:38 -0700 (PDT) In-Reply-To: References: <6A0DE07E22DDAD4C9103DF62FEBC09093B599819@shsmsx102.ccr.corp.intel.com> From: Tetsuro Nakamura Date: Mon, 17 Apr 2017 12:43:38 +0900 Message-ID: To: "users@dpdk.org" Cc: "Lu, Wenzhuo" , Adrien Mazarguil , "Zhao1, Wei" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-users] using rte_flow via tespmd with Intel X552 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 17 Apr 2017 03:43:40 -0000 Hi All, I understand. Then I will wait for the documentation. Anyway, I appreciate your kind response ! Thank you, *From:* Lu, Wenzhuo > *Sent:* Monday, April 17, 2017 10:57 AM > *To:* Tetsuro Nakamura ; users@dpdk.org > *Cc:* Adrien Mazarguil ; Zhao1, Wei < > wei.zhao1@intel.com> > *Subject:* RE: [dpdk-users] using rte_flow via tespmd with Intel X552 > > > > Hi Nakamura, > > > > *From:* Tetsuro Nakamura [mailto:xyz1.8tn@gmail.com ] > *Sent:* Monday, April 17, 2017 10:36 AM > *To:* users@dpdk.org > *Cc:* Adrien Mazarguil; Zhao1, Wei; Lu, Wenzhuo > *Subject:* Re: [dpdk-users] using rte_flow via tespmd with Intel X552 > > > > Dear Adrien and Wenzhuo, > > > > Thank you very much for your kind reply. > > I tried flow_director_filter API directly using testpmd with the same > environment. > > So let me add more information. > > > > - Using pktgen-3.0.13, I prepared 2 flows whose dst-Macs are > 0c:c4:7a:cf:66:11 and 0c:c4:7a:cf:66:12 respectively. > > ``` > > Pktgen> set 0 seqCnt 2 > > Pktgen> seq 0 0 0c:c4:7a:cf:66:11 0c:c4:7a:cf:66:01 192.168.1.1 > 192.168.0.1/24 1234 5678 ipv4 udp 1 64 > > Pktgen> seq 0 0 0c:c4:7a:cf:66:12 0c:c4:7a:cf:66:02 192.168.1.1 > 192.168.0.1/24 1234 5678 ipv4 udp 1 64 > > Pktgen> start 0 > > ``` > > > > - Then I started testpmd with options of "--rxq=3D2 --txq=3D2" and > "--pkt-filter-mode=3Dperfect-mac-vlan". > > - No error had occurred when configuring flow_director_filter. > > - When started, all packets were received in Pktgen. > > ``` > > $sudo ./dpdk-17.04/x86_64-native-linuxapp-gcc/app/testpmd -l 0-4 -n 4 -- > -i --portmask=3D0x3 --nb-cores=3D4 --rxq=3D2 --txq=3D2 > --pkt-filter-mode=3Dperfect-mac-vlan > > > > testpmd> flow_director_filter 0 mode MAC-VLAN add mac 0c:c4:7a:cf:66:11 > vlan 1 flexbytes (0x80,0x00) fwd queue 0 fd_id 1 > > testpmd> flow_director_filter 0 mode MAC-VLAN add mac 0c:c4:7a:cf:66:12 > vlan 1 flexbytes (0x80,0x00) fwd queue 1 fd_id 2 > > testpmd> start > > ``` > > > > - When queue 0 was stopped, no packet was received in Pktgen. > > ``` > > testpmd> stop > > testpmd> port 0 rxq 0 stop > > testpmd> start > > ``` > > > > - When queue 1 was stopped, all packets were received in Pktgen. > > ``` > > testpmd> stop > > testpmd> port 0 rxq 0 start > > testpmd> port 0 rxq 1 stop > > testpmd> start > > ``` > > > > - which (I guess) mean the flow is not supported as you said. > > - The mac argument in flow_director_filter is dst-Mac, right? > > [Wenzhuo] Yes. It=E2=80=99s dst-mac. It=E2=80=99s the benefit of generic = flow API. Using > generic API users do know what fields the input are. But the original on= e, > users have to check the comments and docs J > > > > 2017-04-17 9:55 GMT+09:00 Lu, Wenzhuo : > > Hi, > > > -----Original Message----- > > From: Adrien Mazarguil [mailto:adrien.mazarguil@6wind.com] > > Sent: Friday, April 14, 2017 5:22 PM > > To: Tetsuro Nakamura > > Cc: users@dpdk.org; Lu, Wenzhuo > > Subject: Re: [dpdk-users] using rte_flow via tespmd with Intel X552 > > > > Hi Tetsuro, > > > > On Thu, Apr 13, 2017 at 10:18:28AM +0900, Tetsuro Nakamura wrote: > > > Hi All, > > > > > > I'm now trying to use simple L2 function with "Generic Flow API > (rte_flow)" > > > using testpmd in dpdk-17.02, > > > but it doesn't work with the error below. > > > > > > ----------- > > > $sudo ./dpdk-17.02/x86_64-native-linuxapp-gcc/app/testpmd -l 0-3 -n 4 > > > -- -i > > > --portmask=3D0x3 --nb-cores=3D2 > > > > > > testpmd> flow validate 0 ingress pattern eth / eth dst is > > > testpmd> a0:36:9f:78:30:26 > > > / end actions drop / end > > > Caught error type 9 (specific pattern item): cause: 0x7ffd225adc88, > > > Not supported by L2 tunnel filter > > > testpmd> flow validate 0 ingress pattern eth / eth dst is > > > testpmd> a0:36:9f:78:30:26 > > > > / end actions queue index 0 / end > > > Caught error type 9 (specific pattern item): cause: 0x7ffd225adc88, > > > Not supported by L2 tunnel filter > > > ----------- > > > > > > I tried several other flows and got the same error. > > > I'm using Intel X552 NIC. The firmware-version is 0x800003e7. > > > > > > ----------- > > > $ sudo ethtool -i rename6 > > > driver: ixgbe > > > version: 5.0.4 > > > firmware-version: 0x800003e7 > > > expansion-rom-version: > > > bus-info: 0000:03:00.0 > > > supports-statistics: yes > > > supports-test: yes > > > supports-eeprom-access: yes > > > supports-register-dump: yes > > > supports-priv-flags: no > > > ----------- > > > > > > My question is, > > > am I missing some additional settings to do ? > > > Should I use another firmware version ? > > > # DPDK 17.02 official release note says the tested firmware version > > > was 0x800001cf. > > > # My version, 0x800003e7 is newer, isn't it? > > > > > > I don't think the NIC does't support such simple L2 functions. > > > But if it doesn't, are there any documents that tell us which NIC > > > supports which flow rules in rte_flow? > > > Could you tell me what flows I can try with Intel X552 NIC? > > > > > > Thank you and best regards, > > > > > > Tetsuro Nakamura, NTT > > > > I'm not familiar with ixgbe but this issue reminds me of this thread [1= ], > > particularly the following comment: > > > > "the rte_flow_error returned was not very useful for it does return th= e > > error of the last tried filter-type (L2 tunnel in ixgbe), and not the > error of the > > filter-type that my setup should use (flow director)" > > > > CC'ing Wenzhuo, I think this issue is present in 17.02, has it been > fixed since? > > > > [1] http://dpdk.org/ml/archives/dev/2017-March/059928.html > > +Wei > About the previous discussion, Wei has sent the patch to remove the tpid > in ixgbe. But no improvement of error message yet as I know. > > I think this flow is not supported. Generic flow API is flexible enough, > but not every flow can be supported. The flow is supported or not has > nothing to do with if it's simple. It's limited to HW capability. Wei, do > you have some doc to shared or even has uploaded to the community? Thanks= . > > > > > -- > > Adrien Mazarguil > > 6WIND > > > > > > We have a document about command format when creating flow, but has not > been publicly upload to community. > > I will add a new chapter for this in doc\guides\nics\ixgbe.rst later, > which is about command format when creating flow. > > A specific patch will be send to community later. > > >