DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Gregory Etelson <getelson@nvidia.com>, dev@dpdk.org
Cc: elibr@nvidia.com, asafp@nvidia.com, tmonjalon@nvidia.com,
	Ori Kam <orika@nvidia.com>,
	Aman Singh <aman.deep.singh@intel.com>,
	Yuying Zhang <yuying.zhang@intel.com>
Subject: Re: [PATCH V2 1/2] app/testpmd: change flow rule type
Date: Fri, 2 Jun 2023 21:19:32 +0100	[thread overview]
Message-ID: <4db5b8bb-c546-262b-df67-e96326e4080f@amd.com> (raw)
In-Reply-To: <20230316141934.23181-1-getelson@nvidia.com>

On 3/16/2023 2:19 PM, Gregory Etelson wrote:
> From: Eli Britstein <elibr@nvidia.com>
> 
> Change flow rule type to be uint64_t (instead of currently uint32_t) to
> be able to accommodate larger IDs, as a pre-step towards allowing user-id
> to flows.
> 
> Signed-off-by: Eli Britstein <elibr@nvidia.com>
>

Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>


  parent reply	other threads:[~2023-06-02 20:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22 14:11 [PATCH 1/2] app/testpmd: change " Eli Britstein
2023-02-22 14:11 ` [PATCH 2/2] app/testpmd: user assigned flow ID to flows Eli Britstein
2023-02-22 16:50   ` Thomas Monjalon
2023-03-16 14:19   ` [PATCH V2 1/2] app/testpmd: change flow rule type Gregory Etelson
2023-03-16 14:19     ` [PATCH V2 2/2] app/testpmd: assign custom ID to flow rules Gregory Etelson
2023-06-02 20:19       ` Ferruh Yigit
2023-06-30 10:21         ` Ferruh Yigit
2023-07-04  8:25       ` Ori Kam
2023-07-04 14:40         ` Ferruh Yigit
2023-06-02 20:19     ` Ferruh Yigit [this message]
2023-03-01  1:00 ` [PATCH 1/2] app/testpmd: change rule type Ferruh Yigit

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=4db5b8bb-c546-262b-df67-e96326e4080f@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=aman.deep.singh@intel.com \
    --cc=asafp@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=elibr@nvidia.com \
    --cc=getelson@nvidia.com \
    --cc=orika@nvidia.com \
    --cc=tmonjalon@nvidia.com \
    --cc=yuying.zhang@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).