From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Marvin Liu <yong.liu@intel.com>, tiwei.bie@intel.com
Cc: zhihong.wang@intel.com, dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v4 5/9] net/virtio: free in-order descriptors before device start
Date: Mon, 2 Jul 2018 09:18:18 +0200 [thread overview]
Message-ID: <b74baa0b-b388-43cc-9c0f-c406b583d97e@redhat.com> (raw)
In-Reply-To: <20180630235049.62610-6-yong.liu@intel.com>
On 07/01/2018 01:50 AM, Marvin Liu wrote:
> Add new function for freeing IN_ORDER descriptors. As descriptors will
> be allocated and freed sequentially when IN_ORDER feature was
> negotiated. There will be no need to utilize chain for freed descriptors
> management, only index update is enough.
>
> Signed-off-by: Marvin Liu <yong.liu@intel.com>
>
Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>
next prev parent reply other threads:[~2018-07-02 7:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-30 23:50 [dpdk-dev] [PATCH v4 0/9] support in-order feature Marvin Liu
2018-06-30 23:50 ` [dpdk-dev] [PATCH v4 1/9] vhost: advertise " Marvin Liu
2018-06-30 23:50 ` [dpdk-dev] [PATCH v4 2/9] net/virtio: add in-order feature bit definition Marvin Liu
2018-06-30 23:50 ` [dpdk-dev] [PATCH v4 3/9] net/virtio-user: add unsupported features mask Marvin Liu
2018-06-30 23:50 ` [dpdk-dev] [PATCH v4 4/9] net/virtio-user: add mrg-rxbuf and in-order vdev parameters Marvin Liu
2018-06-30 23:50 ` [dpdk-dev] [PATCH v4 5/9] net/virtio: free in-order descriptors before device start Marvin Liu
2018-07-02 7:18 ` Maxime Coquelin [this message]
2018-06-30 23:50 ` [dpdk-dev] [PATCH v4 6/9] net/virtio: extract common part for in-order functions Marvin Liu
2018-06-30 23:50 ` [dpdk-dev] [PATCH v4 7/9] net/virtio: support in-order Rx and Tx Marvin Liu
2018-06-30 23:50 ` [dpdk-dev] [PATCH v4 8/9] net/virtio: add in-order Rx/Tx into selection Marvin Liu
2018-06-30 23:50 ` [dpdk-dev] [PATCH v4 9/9] net/virtio: advertise support in-order feature Marvin Liu
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=b74baa0b-b388-43cc-9c0f-c406b583d97e@redhat.com \
--to=maxime.coquelin@redhat.com \
--cc=dev@dpdk.org \
--cc=tiwei.bie@intel.com \
--cc=yong.liu@intel.com \
--cc=zhihong.wang@intel.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).