From: Thomas Monjalon <thomas@monjalon.net>
To: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
Cc: dev@dpdk.org, Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [dpdk-dev] [PATCH v3] doc: add timestamp upper limitation in mlx5 guide
Date: Wed, 05 Aug 2020 17:43:34 +0200 [thread overview]
Message-ID: <20010827.CIYFszEg1f@thomas> (raw)
In-Reply-To: <20200805152610.277087-1-thomas@monjalon.net>
05/08/2020 17:26, Thomas Monjalon:
> From: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
>
> Add description about Tx scheduling timestamp upper limit.
> If timestamp exceed the value, it is marked by PMD as being
> into "too-distant-future" and not scheduled at all
> (is being sent without any wait).
>
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>
> Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
> ---
> v2: typo fix
> v3: more typos fixed and small rewording
Applied
prev parent reply other threads:[~2020-08-05 15:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 15:51 [dpdk-dev] [PATCH v2] doc/mlx5: add timestamp upper limitation description Viacheslav Ovsiienko
2020-08-05 15:26 ` [dpdk-dev] [PATCH v3] doc: add timestamp upper limitation in mlx5 guide Thomas Monjalon
2020-08-05 15:43 ` Thomas Monjalon [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=20010827.CIYFszEg1f@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=viacheslavo@mellanox.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).