DPDK patches and discussions
 help / color / mirror / Atom feed
From: Suanming Mou <suanmingm@nvidia.com>
To: "anoobj@marvell.com" <anoobj@marvell.com>,
	"Doherty, Declan" <declan.doherty@intel.com>
Cc: "gakhil@marvell.com" <gakhil@marvell.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: min_mbuf_head/tailroom_req in rte_cryptodev_info
Date: Tue, 9 May 2023 11:53:28 +0000	[thread overview]
Message-ID: <CO6PR12MB5396CD6451AA872B2266BD87C1769@CO6PR12MB5396.namprd12.prod.outlook.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 780 bytes --]

Hi Guys,

Sorry for disturbing you. I have one small question regarding the min_mbuf_head/tailroom_req in rte_cryptodev_info.
I saw you were the people who discussed, reviewed and added that two fields.
IIUC, the two fields provided a hint to the PMD that HW can use(modify) the headroom and tailroom space to improve the performance.
But regarding the space(e.g. headroom) user reserved, should the data offset(sym_op->aead.data.offset) in struct rte_crypto_op also be taken into account?
e.g. if the mbuf in the operation is something like below:
|---headroom--|----op offset---|---payload to process---|---tailroom---|
In that case, what is the headroom mean to HW? Start from real mbuf headroom before op offset or the offset before payload?

Thanks,
Suanming Mou

[-- Attachment #2: Type: text/html, Size: 2742 bytes --]

             reply	other threads:[~2023-05-09 11:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09 11:53 Suanming Mou [this message]
2023-05-09 12:13 ` Anoob Joseph
2023-05-09 13:01   ` Suanming Mou

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=CO6PR12MB5396CD6451AA872B2266BD87C1769@CO6PR12MB5396.namprd12.prod.outlook.com \
    --to=suanmingm@nvidia.com \
    --cc=anoobj@marvell.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=gakhil@marvell.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).