DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Cristian Dumitrescu <cristian.dumitrescu@intel.com>
Cc: dev@dpdk.org
Subject: Re: [PATCH] pipeline: rework optimization pattern for header generation
Date: Mon, 20 Jun 2022 16:10:15 +0200	[thread overview]
Message-ID: <3234652.8hb0ThOEGa@thomas> (raw)
In-Reply-To: <20220616141645.30366-1-cristian.dumitrescu@intel.com>

16/06/2022 16:16, Cristian Dumitrescu:
> The P4 language requires marking a header as valid before any of the
> header fields are written as opposed to after the writes are done.
> Hence, the optimization of replacing the sequence of instructions to
> generate a header by reading it from the table action data with a
> single DMA internal instruction are reworked from "mov all + validate
> -> dma" to "validate + mov all -> dma".
> 
> Signed-off-by: Cristian Dumitrescu <cristian.dumitrescu@intel.com>

Applied, thanks.




      reply	other threads:[~2022-06-20 14:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-16 14:16 Cristian Dumitrescu
2022-06-20 14:10 ` Thomas Monjalon [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=3234652.8hb0ThOEGa@thomas \
    --to=thomas@monjalon.net \
    --cc=cristian.dumitrescu@intel.com \
    --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).