DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Burakov, Anatoly" <anatoly.burakov@intel.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: <dev@dpdk.org>, <vladimir.medvedkin@intel.com>
Subject: Re: [PATCH v2 1/1] doc/ice: document protocol agnostic filtering
Date: Thu, 13 Nov 2025 10:55:48 +0100	[thread overview]
Message-ID: <a3d380e1-cd2f-4953-99f4-f3634accc675@intel.com> (raw)
In-Reply-To: <aRS-Fk088_bRM3gB@bricha3-mobl1.ger.corp.intel.com>

On 11/12/2025 6:04 PM, Bruce Richardson wrote:
> On Wed, Nov 12, 2025 at 11:34:12AM +0000, Anatoly Burakov wrote:
>> Current documentation for protocol agnostic filtering for ICE driver is a
>> bit terse and relies on a lot of assumed knowledge. Document the feature
>> better and make all of the assumptions explicit.
>>
>> Signed-off-by: Anatoly Burakov <anatoly.burakov@intel.com>
>> Acked-by: Vladimir Medvedkin <vladimir.medvedkin@intel.com>
>> ---


>> +
>> +.. code-block:: console
>> +
>> +   python3 flow_parse.py --show -p "mac()/ipv4(src=1.1.1.1,dst=2.2.2.2)/udp()"
>> +
>> +Output:
>> +
>> +   {'flow': {'generic': {'pattern': {'spec': b'00000000000100000000000208004500001c000000000011000001010101020202020000000000080000',
>> +   'mask': b'0000000000000000000000000000000000000000000000000000ffffffffffffffff0000000000000000'}}}}
>> +
> 
> This looks like it should have a code-block tag on it too. Was that a
> deliberate omission? If it should be there, I'll add it on apply.
> 

<snip>

>> +
>> +Spec (packet template):
>> +  000000000001              Destination MAC (6 bytes)
>> +  000000000002              Source MAC (6 bytes)
>> +  0800                      EtherType = IPv4
>> +  4500001c0000000000110000  IPv4 header, protocol = UDP
>> +  01010101                  Source IP = 1.1.1.1
>> +  02020202                  Destination IP = 2.2.2.2
>> +  0000000000080000          UDP header
>> +
> 
> The format of the output in the HTML here is not as above. Again, should
> this have a code-block tag on it?

Yes on both, they were meant to be monospace formatted (not necessarily 
a *code* block but a monospaced block at least).

> 
>> +Mask:
>> +  000000000000              Destination MAC (ignored)
>> +  000000000000              Source MAC (ignored)
>> +  0000                      EtherType (ignored)
>> +  000000000000000000000000  IPv4/UDP header (ignored)
>> +  ffffffff                  Source IP (match all 32 bits)
>> +  ffffffff                  Destination IP (match all 32 bits)
>> +  0000000000000000          UDP header (ignored)
>> +
> <snip>


-- 
Thanks,
Anatoly

  reply	other threads:[~2025-11-13  9:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-29 15:17 [PATCH v1 " Anatoly Burakov
2025-10-29 15:17 ` Medvedkin, Vladimir
2025-10-29 17:20 ` Bruce Richardson
2025-11-12 11:34 ` [PATCH v2 " Anatoly Burakov
2025-11-12 17:04   ` Bruce Richardson
2025-11-13  9:55     ` Burakov, Anatoly [this message]
2025-11-13 10:37       ` Bruce Richardson

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=a3d380e1-cd2f-4953-99f4-f3634accc675@intel.com \
    --to=anatoly.burakov@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=vladimir.medvedkin@intel.com \
    /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).