DPDK patches and discussions
 help / color / mirror / Atom feed
From: Tiwei Bie <tiwei.bie@intel.com>
To: lin li <chuckylinchuckylin@gmail.com>
Cc: dev@dpdk.org, dariusz.stojaczyk@intel.com,
	changpeng.liu@intel.com, Li Lin <lilin24@baidu.com>,
	maxime.coquelin@redhat.com
Subject: Re: [dpdk-dev] [PATCH v4] vhost: support inflight share memory protocol feature
Date: Tue, 21 May 2019 16:46:30 +0800	[thread overview]
Message-ID: <20190521084630.GA20965@___> (raw)
In-Reply-To: <CAF+hgq3+Uxpfpud5qBXS7h69D1GCW0V+ZkBYPCVrhvJfTCHbuw@mail.gmail.com>

On Tue, May 21, 2019 at 04:29:31PM +0800, lin li wrote:
> Tiwei Bie <tiwei.bie@intel.com> 于2019年5月20日周一上午10:14写道:
> >
> > On Fri, May 17, 2019 at 05:47:07PM +0200, Maxime Coquelin wrote:
> > > On 5/5/19 11:02 AM, Li Lin wrote:
> > [...]
> > > >   /**
> > > >    * Device structure contains all configuration information relating
> > > >    * to the device.
> > > > @@ -303,6 +314,7 @@ struct virtio_net {
> > > >     uint32_t                nr_vring;
> > > >     int                     dequeue_zero_copy;
> > > >     struct vhost_virtqueue  *virtqueue[VHOST_MAX_QUEUE_PAIRS * 2];
> > > > +   struct inflight_mem_info inflight_info;
> > > >   #define IF_NAME_SZ (PATH_MAX > IFNAMSIZ ? PATH_MAX : IFNAMSIZ)
> > > >     char                    ifname[IF_NAME_SZ];
> > > >     uint64_t                log_size;
> > >
> > > Do you have some code example using these new APIs?
> > > It would help for reviewing the patch.
> >
> > +1
> I just submitted SPDK-related patches, and you will see how to use new API.

SPDK is another separate project. For the DPDK APIs introduced
in this patch, it would be great to have an example in DPDK to
demonstrate their usage, e.g. examples/vhost_scsi. Besides, the
new APIs also need to take the packed ring into consideration.

Thanks,
Tiwei

  reply	other threads:[~2019-05-21  8:47 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-25  7:56 [dpdk-dev] [PATCH] [resend] " Li Lin
2019-04-25  7:56 ` Li Lin
2019-04-25 10:56 ` lin li
2019-04-25 10:56   ` lin li
2019-04-25 11:10 ` [dpdk-dev] [PATCH v2] " Li Lin
2019-04-25 11:10   ` Li Lin
2019-04-26  9:40   ` [dpdk-dev] [PATCH v3] " Li Lin
2019-04-26  9:40     ` Li Lin
2019-04-28 11:17     ` Tiwei Bie
2019-04-28 11:17       ` Tiwei Bie
2019-04-29  4:07       ` lin li
2019-04-29  4:07         ` lin li
2019-04-29 10:54         ` Tiwei Bie
2019-04-29 10:54           ` Tiwei Bie
2019-04-30  8:37           ` lin li
2019-04-30  8:37             ` lin li
2019-05-05  9:02     ` [dpdk-dev] [PATCH v4] " Li Lin
2019-05-05  9:02       ` Li Lin
2019-05-17 15:47       ` Maxime Coquelin
2019-05-20  2:13         ` Tiwei Bie
2019-05-21  8:29           ` lin li
2019-05-21  8:46             ` Tiwei Bie [this message]
2019-05-22 10:15               ` [dpdk-dev] 答复: " Li,Lin(ACG Cloud)
2019-05-22 11:04         ` Li,Lin(ACG Cloud)
2019-06-12  8:07           ` Maxime Coquelin

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=20190521084630.GA20965@___ \
    --to=tiwei.bie@intel.com \
    --cc=changpeng.liu@intel.com \
    --cc=chuckylinchuckylin@gmail.com \
    --cc=dariusz.stojaczyk@intel.com \
    --cc=dev@dpdk.org \
    --cc=lilin24@baidu.com \
    --cc=maxime.coquelin@redhat.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).