DPDK patches and discussions
 help / color / mirror / Atom feed
From: Kumar Sanghvi <kumars@xilinx.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] Query on VIRTIO_F_IN_ORDER
Date: Mon, 19 Aug 2019 21:44:37 +0000	[thread overview]
Message-ID: <SN6PR02MB393449FBF3FF3DFF65B237F6A4A80@SN6PR02MB3934.namprd02.prod.outlook.com> (raw)

Hi All,

VirtIO-1.1 seems to have VIRTIO_F_IN_ORDER support for Split Virtqueues.

In this regards, does DPDK Virtio and Vhost drivers support VIRTIO_F_IN_ORDER on Split Virtqueues - which allows single used-ring entry to notify a batch of buffers to driver ?
Also, is this feature applicable for both Rx and Tx ?


Thanks,
Kumar.
This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.

                 reply	other threads:[~2019-08-20 15:07 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=SN6PR02MB393449FBF3FF3DFF65B237F6A4A80@SN6PR02MB3934.namprd02.prod.outlook.com \
    --to=kumars@xilinx.com \
    --cc=dev@dpdk.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 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).