DPDK patches and discussions
 help / color / mirror / Atom feed
From: Anup Prabhu <aprabhu@marvell.com>
To: Srikanth Yalavarthi <syalavarthi@marvell.com>,
	Srikanth Yalavarthi <syalavarthi@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Shivah Shankar Shankar Narayan Rao <sshankarnara@marvell.com>,
	Prince Takkar <ptakkar@marvell.com>
Subject: RE: [PATCH v2 3/3] mldev: drop input and output size get APIs
Date: Tue, 3 Oct 2023 06:10:38 +0000	[thread overview]
Message-ID: <BL0PR18MB3748F23FB92942DBDB25B4ECA5C4A@BL0PR18MB3748.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20230920071910.10428-4-syalavarthi@marvell.com>

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



> -----Original Message-----
> From: Srikanth Yalavarthi <syalavarthi@marvell.com>
> Sent: Wednesday, September 20, 2023 12:49 PM
> To: Srikanth Yalavarthi <syalavarthi@marvell.com>
> Cc: dev@dpdk.org; Shivah Shankar Shankar Narayan Rao
> <sshankarnara@marvell.com>; Anup Prabhu <aprabhu@marvell.com>;
> Prince Takkar <ptakkar@marvell.com>
> Subject: [PATCH v2 3/3] mldev: drop input and output size get APIs
> 
> Drop support and use of ML input and output size get functions,
> rte_ml_io_input_size_get and rte_ml_io_output_size_get.
> 
> These functions are not required, as the model buffer size can be computed
> from the fields of updated rte_ml_io_info structure.
> 
> Signed-off-by: Srikanth Yalavarthi <syalavarthi@marvell.com>
>
Acked-by: Anup Prabhu <aprabhu@marvell.com>

[-- Attachment #2: winmail.dat --]
[-- Type: application/ms-tnef, Size: 35422 bytes --]

  reply	other threads:[~2023-10-03  6:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-30 15:52 [PATCH v1 0/3] Spec changes to support multi I/O models Srikanth Yalavarthi
2023-08-30 15:53 ` [PATCH v1 1/3] mldev: add support for arbitrary shape dimensions Srikanth Yalavarthi
2023-08-30 15:53 ` [PATCH v1 2/3] mldev: introduce support for IO layout Srikanth Yalavarthi
2023-08-30 15:53 ` [PATCH v1 3/3] mldev: drop input and output size get APIs Srikanth Yalavarthi
2023-09-20  7:19 ` [PATCH v2 0/3] Spec changes to support multi I/O models Srikanth Yalavarthi
2023-09-20  7:19   ` [PATCH v2 1/3] mldev: add support for arbitrary shape dimensions Srikanth Yalavarthi
2023-09-20  7:19   ` [PATCH v2 2/3] mldev: introduce support for IO layout Srikanth Yalavarthi
2023-09-20  7:19   ` [PATCH v2 3/3] mldev: drop input and output size get APIs Srikanth Yalavarthi
2023-10-03  6:10     ` Anup Prabhu [this message]
2023-09-27 18:11 ` [PATCH v3 0/4] Spec changes to support multi I/O models Srikanth Yalavarthi
2023-09-27 18:11   ` [PATCH v3 1/4] mldev: add support for arbitrary shape dimensions Srikanth Yalavarthi
2023-09-27 18:11   ` [PATCH v3 2/4] mldev: introduce support for IO layout Srikanth Yalavarthi
2023-09-27 18:11   ` [PATCH v3 3/4] mldev: drop input and output size get APIs Srikanth Yalavarthi
2023-09-27 18:11   ` [PATCH v3 4/4] mldev: update release notes for 23.11 Srikanth Yalavarthi
2023-09-29  3:39     ` Jerin Jacob
2023-10-02  9:59       ` [EXT] " Srikanth Yalavarthi
2023-10-02  9:58 ` [PATCH v4 0/3] Spec changes to support multi I/O models Srikanth Yalavarthi
2023-10-02  9:58   ` [PATCH v4 1/3] mldev: add support for arbitrary shape dimensions Srikanth Yalavarthi
2023-10-04 14:42     ` Anup Prabhu
2023-10-05  9:12     ` Shivah Shankar Shankar Narayan Rao
2023-10-02  9:58   ` [PATCH v4 2/3] mldev: introduce support for IO layout Srikanth Yalavarthi
2023-10-05  9:10     ` Shivah Shankar Shankar Narayan Rao
2023-10-02  9:58   ` [PATCH v4 3/3] mldev: drop input and output size get APIs Srikanth Yalavarthi
2023-10-03  6:12     ` Anup Prabhu
2023-10-05  9:06     ` Shivah Shankar Shankar Narayan Rao
2023-10-11 14:45   ` [PATCH v4 0/3] Spec changes to support multi I/O models Thomas Monjalon

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=BL0PR18MB3748F23FB92942DBDB25B4ECA5C4A@BL0PR18MB3748.namprd18.prod.outlook.com \
    --to=aprabhu@marvell.com \
    --cc=dev@dpdk.org \
    --cc=ptakkar@marvell.com \
    --cc=sshankarnara@marvell.com \
    --cc=syalavarthi@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).