DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matan Azrad <matan@nvidia.com>
To: Asaf Penso <asafp@nvidia.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "NBU-Contact-Thomas Monjalon (EXTERNAL)" <thomas@monjalon.net>,
	Slava Ovsiienko <viacheslavo@nvidia.com>,
	Raslan Darawsheh <rasland@nvidia.com>
Subject: RE: [PATCH v2] net/mlx5: add stub functions to null drv ops
Date: Thu, 29 Dec 2022 08:57:50 +0000	[thread overview]
Message-ID: <DM4PR12MB538986FF955F6E741F998523DFF39@DM4PR12MB5389.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20221228183727.3689455-1-asafp@nvidia.com>



From: Asaf Penso <asafp@nvidia.com>
> There are several functions implementation that queries the drv type to
> understand which fops function to use.
> In case the type is DV, the function gets the concrete DV function and calls it.
> In case it’s not, the function returns an error.
> 
> The current implementation is not flexible enough and will not support future
> concrete functions in a good way.
> 
> This patch adds more stub functions that include error handling and are assigned
> to the null drv ops struct.
> This allows the functions to always call the virtual function without basing the
> decision on a specific drv type.
> 
> Signed-off-by: Asaf Penso <asafp@nvidia.com>
Acked-by: Matan Azrad <matan@nvidia.com>

  reply	other threads:[~2022-12-29  8:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23  8:55 [dpdk-dev] [PATCH 1/1] " Asaf Penso
2022-12-28 18:37 ` [PATCH v2] " Asaf Penso
2022-12-29  8:57   ` Matan Azrad [this message]
2023-01-04 11:43   ` Raslan Darawsheh

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=DM4PR12MB538986FF955F6E741F998523DFF39@DM4PR12MB5389.namprd12.prod.outlook.com \
    --to=matan@nvidia.com \
    --cc=asafp@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=rasland@nvidia.com \
    --cc=thomas@monjalon.net \
    --cc=viacheslavo@nvidia.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).