From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Dariusz Sosnowski <dsosnowski@nvidia.com>,
Thomas Monjalon <thomas@monjalon.net>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Cc: dev@dpdk.org, Konstantin Ananyev <konstantin.ananyev@huawei.com>
Subject: Re: [PATCH v3 0/4] ethdev: rework config restore
Date: Fri, 11 Oct 2024 22:25:17 +0100 [thread overview]
Message-ID: <72d085b4-c724-46ed-861e-bd4e7eab8b14@amd.com> (raw)
In-Reply-To: <20241011185137.277874-1-dsosnowski@nvidia.com>
On 10/11/2024 7:51 PM, Dariusz Sosnowski wrote:
> This patch series reworks the config restore procedure,
> so that drivers are able to enable/disable certain parts of it.
> Drivers can provide get_restore_flags() callback,
> which will indicate to ethdev library what configuration to restore.
>
> If callback is not defined, then ethdev assumes that
> all configuration must be restored, preserving the current behavior for all drivers.
>
> This patch series also includes implementation of get_restore_flags()
> for mlx5 PMD, which does not require config restore.
>
> RFC: https://inbox.dpdk.org/dev/20240918092201.33772-1-dsosnowski@nvidia.com/
>
> v3:
> - Change type for restore flags to uint64_t.
> - Return restore flags from rte_eth_get_restore_flags() directly,
> instead of returning through pointer.
> v2:
> - Fix typos in API docs.
>
> Dariusz Sosnowski (4):
> ethdev: rework config restore
> ethdev: add get restore flags driver callback
> ethdev: restore config only when requested
> net/mlx5: disable config restore
>
For series,
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
Series applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2024-10-11 21:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 9:20 [PATCH " Dariusz Sosnowski
2024-10-11 9:21 ` [PATCH 1/4] " Dariusz Sosnowski
2024-10-11 9:21 ` [PATCH 2/4] ethdev: add get restore flags driver callback Dariusz Sosnowski
2024-10-11 9:21 ` [PATCH 3/4] ethdev: restore config only when requested Dariusz Sosnowski
2024-10-11 9:21 ` [PATCH 4/4] net/mlx5: disable config restore Dariusz Sosnowski
2024-10-11 9:33 ` [PATCH v2 0/4] ethdev: rework " Dariusz Sosnowski
2024-10-11 9:33 ` [PATCH v2 1/4] " Dariusz Sosnowski
2024-10-11 9:33 ` [PATCH v2 2/4] ethdev: add get restore flags driver callback Dariusz Sosnowski
2024-10-11 12:54 ` Konstantin Ananyev
2024-10-11 15:30 ` Dariusz Sosnowski
2024-10-11 9:33 ` [PATCH v2 3/4] ethdev: restore config only when requested Dariusz Sosnowski
2024-10-11 9:33 ` [PATCH v2 4/4] net/mlx5: disable config restore Dariusz Sosnowski
2024-10-11 18:51 ` [PATCH v3 0/4] ethdev: rework " Dariusz Sosnowski
2024-10-11 18:51 ` [PATCH v3 1/4] " Dariusz Sosnowski
2024-10-11 18:51 ` [PATCH v3 2/4] ethdev: add get restore flags driver callback Dariusz Sosnowski
2024-10-11 18:51 ` [PATCH v3 3/4] ethdev: restore config only when requested Dariusz Sosnowski
2024-10-11 18:51 ` [PATCH v3 4/4] net/mlx5: disable config restore Dariusz Sosnowski
2024-10-11 21:25 ` Ferruh Yigit [this message]
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=72d085b4-c724-46ed-861e-bd4e7eab8b14@amd.com \
--to=ferruh.yigit@amd.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=konstantin.ananyev@huawei.com \
--cc=thomas@monjalon.net \
/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).