DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matteo Lanzuisi <m.lanzuisi@resi.it>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Using example flow_filtering
Date: Wed, 19 Sep 2018 12:20:54 +0200	[thread overview]
Message-ID: <be648eed-a312-3cd4-0429-56efde80cd76@resi.it> (raw)
In-Reply-To: <d8e44202-febd-4c31-54e3-abfb8ef0389a@resi.it>

Any suggestion about this issue?

Il 12/09/2018 09:38, Matteo Lanzuisi ha scritto:
> Hi all,
>
> maybe a bug or something I'm doing wrong: I'm using the example 
> flow_filtering on a RedHat 7.5, kernel 3.10.0-862.6.3.el7.x86_64 with 
> i40e and X710.
>
> DPDK is 18.08 and configuration is x86_64-native-linuxapp-gcc
>
> I changed the SRC_IP and DST_IP this way
>
> #define SRC_IP ((83<<24) + (175<<16) + (7<<8) + 228) /* src ip = 
> 83.175.7.228 */
> #define DEST_IP ((83<<24) + (175<<16) + (7<<8) + 226) /* dest ip = 
> 83.175.7.226 */
>
> for test purpose and set EMPTY_MASK to both.
>
> If I understood well, putting EMPTY_MASK on both, all incoming traffic 
> is going to be sent to queue 1 (selected_queue) but all I have is that 
> all packets are sent to queue 0 (MACs are 00:00:00:00:00:00 in my 
> sample capture)
>
> src=00:00:00:00:00:00 - dst=00:00:00:00:00:00 - queue=0x0
> src=00:00:00:00:00:00 - dst=00:00:00:00:00:00 - queue=0x0
> src=00:00:00:00:00:00 - dst=00:00:00:00:00:00 - queue=0x0
> src=00:00:00:00:00:00 - dst=00:00:00:00:00:00 - queue=0x0
>
> Am I doing something wrong?
>
> Thank you and regards.
>
> Matteo
>
>
>

-- 


Descrizione: resi.gif

*Matteo Lanzuisi*

/Business Unit ICT/

/
/RESI Informatica S.p.A.
Via Pontina Km 44,044
04011 Aprilia (LT) - Italy
*Tel:*+39 06 92710339
*Mobile:*+39 3355686712
*Fax:*+39 06 92710208

*Email:*m.lanzuisi@resi.it
*Web:*www.resi.it <blocked::http://www.resi.it/>**

Descrizione: resi-group.gif width= <http://www.resi-group.com/>

_ _ _ _ _ _ _ _ _ _ _ _

*Nota di riservatezza:*Ai sensi del Decreto Legislativo n. 196/2003, 
"Codice in materia di Protezione dei dati personali", si precisa che le 
informazioni contenute in questo messaggio e negli eventuali allegati 
sono riservate e per uso esclusivo del destinatario. Persone diverse 
dallo stesso non possono copiare o distribuire il messaggio a terzi. 
Chiunque riceva questo messaggio per errore è pregato di distruggerlo e 
di informare immediatamente il mittente. Grazie.


*Confidentiality Notice:* Accordingly to Italian legislative decree n. 
196/2003 concerning privacy, the information contained in this e-mail is 
intended for the named recipients only. It may contain privileged and 
confidential information and if you are not an intended recipient, you 
must not copy, distribute or take any action in reliance on it. If you 
have received this e-mail in error, please notify the sender by e-mail 
and delete the e-mail and any copies of it. Thank you.

*P*****Please consider the environment before printing this mail. 
Rispettate l’ambiente e stampate questa email solo in caso di reale 
necessità

      reply	other threads:[~2018-09-19 10:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12  7:38 Matteo Lanzuisi
2018-09-19 10:20 ` Matteo Lanzuisi [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=be648eed-a312-3cd4-0429-56efde80cd76@resi.it \
    --to=m.lanzuisi@resi.it \
    --cc=dev@dpdk.org \
    /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).