DPDK patches and discussions
 help / color / mirror / Atom feed
From: Radu Nicolau <radu.nicolau@intel.com>
To: Akhil Goyal <gakhil@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "kai.ji@intel.com" <kai.ji@intel.com>,
	Fan Zhang <fanzhang.oss@gmail.com>
Subject: Re: [EXTERNAL] [RFC] lib/cryptodev: update API documentation for aux_flags
Date: Fri, 12 Sep 2025 15:01:28 +0100	[thread overview]
Message-ID: <114c4b2b-f619-4a12-ac0c-adca09fe6033@intel.com> (raw)
In-Reply-To: <CO6PR18MB4484F38CE9989A01F49C8CF7D808A@CO6PR18MB4484.namprd18.prod.outlook.com>

Hi Akhil,

Thanks for looking at this.

On 12-Sep-25 2:05 PM, Akhil Goyal wrote:
> Hi Radu,
>
>> Update the API documentation description of rte_crypto_op field
>> aux_flags as to allow PMDs to define driver-specific flags.
> Can you give examples of the flags that you want to add for driver specific work?
> I believe adding driver specific things here may not be good.
> May be we can discuss the specific flags and define them as common for all PMDs.

The flags we have in mind are very PMD specific i.e. controlling 
specific hardware behavior so they will not be suitable to be added to 
the common flags.

Seeing that aux_flags are not that strongly defined and seeing that they 
are already potentially used for PMD specific values my reasoning was to 
formalize this possibility of usage

aux_flags are used here to potentially carry a value that is not covered 
in the common API aux_flags definitions:

https://git.dpdk.org/dpdk/tree/drivers/crypto/cnxk/cn20k_cryptodev_ops.c#n857


Regards,

Radu


  reply	other threads:[~2025-09-12 14:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-27  9:43 Radu Nicolau
2025-09-12 13:05 ` [EXTERNAL] " Akhil Goyal
2025-09-12 14:01   ` Radu Nicolau [this message]
2025-09-12 14:56     ` Akhil Goyal
2025-09-12 15:14       ` Radu Nicolau
2025-09-12 17:08         ` Akhil Goyal

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=114c4b2b-f619-4a12-ac0c-adca09fe6033@intel.com \
    --to=radu.nicolau@intel.com \
    --cc=dev@dpdk.org \
    --cc=fanzhang.oss@gmail.com \
    --cc=gakhil@marvell.com \
    --cc=kai.ji@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).