From: Thomas Monjalon <thomas@monjalon.net>
To: Viacheslav Ovsiienko <viacheslavo@nvidia.com>, rasland@nvidia.com
Cc: dev@dpdk.org
Subject: Re: [PATCH] net/mlx5: add timestamp ascending order error statistics
Date: Mon, 12 Jun 2023 20:03:59 +0200 [thread overview]
Message-ID: <6914095.18pcnM708K@thomas> (raw)
In-Reply-To: <20230420081835.19927-1-viacheslavo@nvidia.com>
This patch is marked "Awaiting Upstream" in patchwork,
but it doesn't seem merged anywhere.
Please check its status.
20/04/2023 10:18, Viacheslav Ovsiienko:
> The ConnectX NICs support packet send scheduling on specified
> moment of time. Application can set the desired timestamp value
> in dynamic mbuf field and driver will push the special WAIT WQE
> to the hardware queue in order to suspend the entire queue
> operations till the specified time moment, then PMD pushes the
> regular WQE for packet sending.
>
> In the following packets the scheduling can be requested again,
> with different timestamps, and driver pushes WAIT WQE accordingly.
> The timestamps should be provided by application in ascending
> order as packets are queued to the hardware queue, otherwise
> hardware would not be able to perform scheduling correctly -
> it discovers the WAIT WQEs in order as they were pushed, there is
> no any reordering - neither in PMD, not in the NIC, and, obviously,
> the regular hardware can't work as time machine and wait for some
> elapsed moment in the past.
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@nvidia.com>
next prev parent reply other threads:[~2023-06-12 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-20 8:18 [PATCH] net/mlx5: add timestamp ascending order error statistics Viacheslav Ovsiienko
2023-06-12 18:03 ` Thomas Monjalon [this message]
2023-06-19 9:07 ` 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=6914095.18pcnM708K@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=rasland@nvidia.com \
--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 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.