From: Simon Horman <horms@kernel.org>
To: Tariq Toukan <tariqt@nvidia.com>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>,
Gal Pressman <gal@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>,
Cosmin Ratiu <cratiu@nvidia.com>
Subject: Re: [PATCH net-next V2 3/6] net/mlx5: hw counters: Replace IDR+lists with xarray
Date: Fri, 4 Oct 2024 09:58:44 +0100 [thread overview]
Message-ID: <20241004085844.GA1310185@kernel.org> (raw)
In-Reply-To: <20241001103709.58127-4-tariqt@nvidia.com>
On Tue, Oct 01, 2024 at 01:37:06PM +0300, Tariq Toukan wrote:
> From: Cosmin Ratiu <cratiu@nvidia.com>
...
> +/* Synchronization notes
> + *
> + * Access to counter array:
> + * - create - mlx5_fc_create() (user context)
> + * - inserts the counter into the xarray.
> + *
> + * - destroy - mlx5_fc_destroy() (user context)
> + * - erases the counter from the xarray and releases it.
> + *
> + * - query mlx5_fc_query(), mlx5_fc_query_cached{,_raw}() (user context)
> + * - user should not access a counter after destroy.
> + *
> + * - bulk query (single thread workqueue context)
> + * - create: query relies on 'lastuse' to avoid updating counters added
> + * around the same time as the current bulk cmd.
> + * - destroy: destroyed counters will not be accessed, even if they are
> + * destroyed during a bulk query command.
> + */
> +static void mlx5_fc_stats_query_all_counters(struct mlx5_core_dev *dev)
> {
> struct mlx5_fc_stats *fc_stats = dev->priv.fc_stats;
> - bool query_more_counters = (first->id <= last_id);
> - int cur_bulk_len = fc_stats->bulk_query_len;
> + u32 bulk_len = fc_stats->bulk_query_len;
> + XA_STATE(xas, &fc_stats->counters, 0);
> u32 *data = fc_stats->bulk_query_out;
> - struct mlx5_fc *counter = first;
> + struct mlx5_fc *counter;
> + u32 last_bulk_id = 0;
> + u64 bulk_query_time;
> u32 bulk_base_id;
> - int bulk_len;
> int err;
>
> - while (query_more_counters) {
> - /* first id must be aligned to 4 when using bulk query */
> - bulk_base_id = counter->id & ~0x3;
> -
> - /* number of counters to query inc. the last counter */
> - bulk_len = min_t(int, cur_bulk_len,
> - ALIGN(last_id - bulk_base_id + 1, 4));
> -
> - err = mlx5_cmd_fc_bulk_query(dev, bulk_base_id, bulk_len,
> - data);
> - if (err) {
> - mlx5_core_err(dev, "Error doing bulk query: %d\n", err);
> - return;
> - }
> - query_more_counters = false;
> -
> - list_for_each_entry_from(counter, &fc_stats->counters, list) {
> - int counter_index = counter->id - bulk_base_id;
> - struct mlx5_fc_cache *cache = &counter->cache;
> -
> - if (counter->id >= bulk_base_id + bulk_len) {
> - query_more_counters = true;
> - break;
> + xas_lock(&xas);
> + xas_for_each(&xas, counter, U32_MAX) {
> + if (xas_retry(&xas, counter))
> + continue;
> + if (unlikely(counter->id >= last_bulk_id)) {
> + /* Start new bulk query. */
> + /* First id must be aligned to 4 when using bulk query. */
> + bulk_base_id = counter->id & ~0x3;
> + last_bulk_id = bulk_base_id + bulk_len;
> + /* The lock is released while querying the hw and reacquired after. */
> + xas_unlock(&xas);
> + /* The same id needs to be processed again in the next loop iteration. */
> + xas_reset(&xas);
> + bulk_query_time = jiffies;
> + err = mlx5_cmd_fc_bulk_query(dev, bulk_base_id, bulk_len, data);
> + if (err) {
> + mlx5_core_err(dev, "Error doing bulk query: %d\n", err);
> + return;
> }
> -
> - update_counter_cache(counter_index, data, cache);
> + xas_lock(&xas);
> + continue;
> }
> + /* Do not update counters added after bulk query was started. */
Hi Cosmin and Tariq,
I'm sorry if it is obvious, but I'm wondering if you could explain further
the relationship between the if block above, where bulk_query_time (and
bulk_base_id) is initialised and if block below, which is conditional on
bulk_query_time.
> + if (time_after64(bulk_query_time, counter->cache.lastuse))
> + update_counter_cache(counter->id - bulk_base_id, data,
> + &counter->cache);
> }
> + xas_unlock(&xas);
> }
...
next prev parent reply other threads:[~2024-10-04 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 10:37 [PATCH net-next V2 0/6] net/mlx5: hw counters refactor Tariq Toukan
2024-10-01 10:37 ` [PATCH net-next V2 1/6] net/mlx5: hw counters: Make fc_stats & fc_pool private Tariq Toukan
2024-10-01 10:37 ` [PATCH net-next V2 2/6] net/mlx5: hw counters: Use kvmalloc for bulk query buffer Tariq Toukan
2024-10-01 10:37 ` [PATCH net-next V2 3/6] net/mlx5: hw counters: Replace IDR+lists with xarray Tariq Toukan
2024-10-04 8:58 ` Simon Horman [this message]
2024-10-04 9:32 ` Cosmin Ratiu
2024-10-04 10:34 ` Simon Horman
2024-10-01 10:37 ` [PATCH net-next V2 4/6] net/mlx5: hw counters: Drop unneeded cacheline alignment Tariq Toukan
2024-10-01 10:37 ` [PATCH net-next V2 5/6] net/mlx5: hw counters: Don't maintain a counter count Tariq Toukan
2024-10-01 10:37 ` [PATCH net-next V2 6/6] net/mlx5: hw counters: Remove mlx5_fc_create_ex Tariq Toukan
2024-10-04 18:50 ` [PATCH net-next V2 0/6] net/mlx5: hw counters refactor patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2024-10-05 8:17 [PATCH net-next V2 3/6] net/mlx5: hw counters: Replace IDR+lists with xarray kernel test robot
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=20241004085844.GA1310185@kernel.org \
--to=horms@kernel.org \
--cc=cratiu@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=kuba@kernel.org \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.