All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Edmondson <david.edmondson@oracle.com>
To: Parav Pandit <parav@nvidia.com>
Cc: shahafs@nvidia.com, hengqi@linux.alibaba.com,
	virtio@lists.oasis-open.org, virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [PATCH requirements 6/7] net-features: Add packet timestamp requirements
Date: Mon, 14 Aug 2023 12:59:37 +0100	[thread overview]
Message-ID: <m2o7j97s28.fsf@oracle.com> (raw)
In-Reply-To: <20230724033421.249893-7-parav@nvidia.com>


On Monday, 2023-07-24 at 06:34:20 +03, Parav Pandit wrote:
> Add tx and rx packet timestamp requirements.
>
> Signed-off-by: Parav Pandit <parav@nvidia.com>

Acked-by: David Edmondson <david.edmondson@oracle.com>

> ---
>  net-workstream/features-1.4.md | 26 ++++++++++++++++++++++++++
>  1 file changed, 26 insertions(+)
>
> diff --git a/net-workstream/features-1.4.md b/net-workstream/features-1.4.md
> index d228462..37820b6 100644
> --- a/net-workstream/features-1.4.md
> +++ b/net-workstream/features-1.4.md
> @@ -10,6 +10,7 @@ together is desired while updating the virtio net interface.
>  2. Low latency tx and rx virtqueues for PCI transport
>  3. Virtqueue notification coalescing re-arming support
>  4  Virtqueue receive flow filters (RFF)
> +5. Device timestamp for tx and rx packets
>  
>  # 3. Requirements
>  ## 3.1 Device counters
> @@ -280,3 +281,28 @@ struct virtio_net_rff_delete {
>  	u8 padding[2];
>  	le32 flow_id;
>  };
> +
> +## 3.5 Packet timestamp
> +1. Device should provide transmit timestamp and receive timestamp of the packets
> +   at per packet level when the device is enabled.
> +2. Device should provide the current free running clock in the least latency
> +   possible using an MMIO register read of 64-bit to have the least jitter.
> +3. Device should provide the current frequency and the frequency unit for the
> +   software to synchronize the reference point of software and the device using
> +   a control vq command.
> +
> +### 3.5.1 Transmit timestamp
> +1. Transmit completion must contain a packet transmission timestamp when the
> +   device is enabled for it.
> +2. The device should record the packet transmit timestamp in the completion at
> +   the farthest egress point towards the network.
> +3. The device must provide a transmit packet timestamp in a single DMA
> +   transaction along with the rest of the transmit completion fields.
> +
> +### 3.5.2 Receive timestamp
> +1. Receive completion must contain a packet reception timestamp when the device
> +   is enabled for it.
> +2. The device should record the received packet timestamp at the closet ingress
> +   point of reception from the network.
> +3. The device should provide a receive packet timestamp in a single DMA
> +   transaction along with the rest of the receive completion fields.
-- 
Do not leave the building.

This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.

In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.

Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/


  parent reply	other threads:[~2023-08-14 11:59 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-24  3:34 [virtio-comment] [PATCH requirements 0/7] virtio net new features requirements Parav Pandit
2023-07-24  3:34 ` [virtio-comment] [PATCH requirements 1/7] net-features: Add requirements document for release 1.4 Parav Pandit
2023-08-08  8:16   ` David Edmondson
2023-08-14  5:17     ` Parav Pandit
2023-08-14 11:53       ` David Edmondson
2023-08-14 11:56   ` David Edmondson
2023-07-24  3:34 ` [virtio-comment] [PATCH requirements 2/7] net-features: Add low latency transmit queue requirements Parav Pandit
2023-08-08  8:24   ` David Edmondson
2023-08-10 19:05   ` [virtio-comment] RE: [EXT] [virtio] " Satananda Burla
2023-08-15  5:51     ` Parav Pandit
2023-08-14 11:55   ` [virtio-comment] " David Edmondson
2023-07-24  3:34 ` [virtio-comment] [PATCH requirements 3/7] net-features: Add low latency receive " Parav Pandit
2023-08-08  8:32   ` David Edmondson
2023-08-14 11:54   ` David Edmondson
2023-08-15  4:45     ` Parav Pandit
2023-07-24  3:34 ` [virtio-comment] [PATCH requirements 4/7] net-features: Add notification coalescing requirements Parav Pandit
2023-08-14 11:57   ` David Edmondson
2023-07-24  3:34 ` [virtio-comment] [PATCH requirements 5/7] net-features: Add n-tuple receive flow filters requirements Parav Pandit
2023-08-01  8:33   ` [virtio-comment] " Parav Pandit
2023-08-02  6:44     ` Parav Pandit
2023-08-02 15:32       ` Heng Qi
2023-08-03 10:01         ` Parav Pandit
2023-08-03 13:11           ` [virtio-comment] Re: [virtio] " Heng Qi
2023-08-02  7:17   ` [virtio-comment] RE: [EXT] [virtio] " Satananda Burla
2023-08-02  8:14     ` Parav Pandit
2023-08-02 18:32       ` Satananda Burla
2023-08-04  7:32         ` Parav Pandit
2023-08-02 15:25   ` [virtio-comment] " Heng Qi
2023-08-03  9:59     ` [virtio-comment] " Parav Pandit
2023-08-03 13:07       ` [virtio-comment] " Heng Qi
2023-08-04  6:20         ` [virtio-comment] " Parav Pandit
2023-08-04  7:17           ` [virtio-comment] " Heng Qi
2023-08-04  7:30             ` [virtio-comment] " Parav Pandit
2023-08-04  7:51               ` [virtio-comment] Re: [virtio] " Heng Qi
2023-08-07  7:22                 ` Heng Qi
2023-08-08  7:13                   ` Parav Pandit
2023-08-08  8:18                     ` [virtio-comment] Re: [virtio] " Heng Qi
2023-08-08  8:21       ` [virtio-comment] " Heng Qi
2023-08-14  5:15         ` [virtio-comment] " Parav Pandit
2023-08-14  6:18           ` [virtio-comment] " Heng Qi
2023-08-14  6:35             ` [virtio-comment] " Parav Pandit
2023-07-24  3:34 ` [virtio-comment] [PATCH requirements 6/7] net-features: Add packet timestamp requirements Parav Pandit
2023-08-09  8:35   ` [virtio-comment] Re: [virtio] " Xuan Zhuo
2023-08-10  6:56     ` Jason Wang
2023-08-15  6:13       ` Parav Pandit
     [not found]       ` <CAF=yD-+LMY3yE3qtd4vHc8CGOz6UAf4njM2QiZcajrQgL=KZRQ@mail.gmail.com>
2023-08-14  2:54         ` Jason Wang
2023-08-15  6:26         ` Parav Pandit
     [not found]           ` <CAF=yD-LXtrQeW0GnTR0BeDuExN5aBLC4dGEfdWbjtxmhNY2G6g@mail.gmail.com>
2023-08-16  4:10             ` Parav Pandit
2023-08-14 13:06     ` [virtio-comment] " Parav Pandit
2023-08-15  2:47       ` [virtio-comment] " Xuan Zhuo
2023-08-15  4:01         ` [virtio-comment] " Parav Pandit
2023-08-15  6:01           ` [virtio-comment] " Xuan Zhuo
2023-08-15  6:09             ` [virtio-comment] " Parav Pandit
2023-08-15  9:44               ` [virtio-comment] " Xuan Zhuo
2023-08-14 11:59   ` David Edmondson [this message]
2023-07-24  3:34 ` [virtio-comment] [PATCH requirements 7/7] net-features: Add header data split requirements Parav Pandit
2023-08-10 19:19   ` [virtio-comment] RE: [EXT] [virtio] " Satananda Burla
2023-08-14 12:00   ` [virtio-comment] " David Edmondson
     [not found]     ` <CA+FuTSeguCKk4zxZ0=Ebr1phZhF9kssHeGPn2eZj6SRNv2ewsA@mail.gmail.com>
2023-08-14 13:09       ` [virtio-comment] Re: [virtio] " David Edmondson
2023-08-14 13:28         ` [virtio-comment] " Parav Pandit
2023-08-14 13:56           ` [virtio-comment] " David Edmondson
2023-08-15  4:41             ` [virtio-comment] " Parav Pandit
  -- strict thread matches above, loose matches on Subject: below --
2023-06-01 22:02 [virtio-comment] [PATCH requirements 0/7] virtio net new features requirements Parav Pandit
2023-06-01 22:03 ` [virtio-comment] [PATCH requirements 6/7] net-features: Add packet timestamp requirements Parav Pandit
2023-06-06 22:40   ` Michael S. Tsirkin
2023-06-06 22:51     ` Parav Pandit
2023-06-06 23:08       ` Michael S. Tsirkin

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=m2o7j97s28.fsf@oracle.com \
    --to=david.edmondson@oracle.com \
    --cc=hengqi@linux.alibaba.com \
    --cc=parav@nvidia.com \
    --cc=shahafs@nvidia.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=virtio@lists.oasis-open.org \
    /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.