Hi,
> Start from reading https://doc.dpdk.org/guides/prog_guide/rte_flow.html
> eg Table 12.22
>
And here's the painful news, the Mellanox cards we're using do not
support RAW flow items, which means I can't make use of the features
explained in the table 12.22
> But in my mind, as already
Yes, I meant bytes. Thanks Tom.
If you deal with encrypted traffic you can use the payload as random
data and spread it using flow director.
Constructing flow rules is painful process and be prepared that you case
might not work if it is not coverd by test scenarios in DTS.
Also you will have
He means bytes.
I think some drivers only allow the flexible bytes to start after the
actual matching though, eg TCP header. So check for that. I'd contact
Sprayer authors to ask how they did it if I were you.
Do you have a specific NIC in mind? Mellanox's ones are pretty powerful,
it may
Do you mean bit or bytes? 'b' refers to bit, maybe you meant bytes? As
for the network traffic type, we're capturing financial market traffic
over TCP/UDP, nothing really fancy.
Thanks
Il 8/18/20 3:50 PM, Pawel Wodkowski ha scritto:
> Flexible payload matching (aka RAW in flow API) works up to
Flexible payload matching (aka RAW in flow API) works up to first 64b of the
packet - at least in e1000, ixgbe and i40e.
It will be easier if you can provide some details about you network
traffic.
Paweł
On 18.08.2020 14:40, Filip Janiszewski wrote:
Hi,
We had a look at that, and decided
Hi,
We had a look at that, and decided that it might be a bit too
complicated to implement in our SW and will not work in a performant way
as we might wish, ideally we're looking for a simple approach even if
not ideal..
So, I was wondering if we can get at least a "fair" distribution (no
round
Hi Filip,
This is not possible, but you may use the idea of Sprayer
(http://www.gta.ufrj.br/ftp/gta/TechReports/SCC18d.pdf) to dispatch
packets randomly (use RSS on the checksum).
However, in our paper RSS++
(https://www.diva-portal.org/smash/get/diva2:1371780/FULLTEXT01.pdf) we
show it's
Hi,
Is there a way in DPDK to configure the NIC to distribute the incoming
packets to multiple queues in a round robin fashion? Without taking into
account the payload/headers or type of packet, just plain round robin
distribution to multiple queues.
I'm struggling to obtain a fair mechanism
