From: Tiwei Bie <tiwei.bie@intel.com>
To: Maxime Coquelin <maxime.coquelin@redhat.com>
Cc: dev@dpdk.org, yliu@fridaylinux.org,
Zhihong Wang <zhihong.wang@intel.com>,
Zhiyong Yang <zhiyong.yang@intel.com>,
Santosh Shukla <santosh.shukla@caviumnetworks.com>,
Jerin Jacob <jerin.jacob@caviumnetworks.com>,
hemant.agrawal@nxp.com
Subject: Re: [dpdk-dev] [PATCH] vhost: adaptively batch small guest memory copies
Date: Fri, 1 Sep 2017 18:33:23 +0800 [thread overview]
Message-ID: <20170901103322.GA10109@debian-ZGViaWFuCg> (raw)
In-Reply-To: <8697fb77-a1d6-c3de-2bc4-2a9956fbad36@redhat.com>
On Fri, Sep 01, 2017 at 11:45:42AM +0200, Maxime Coquelin wrote:
> On 08/24/2017 04:19 AM, Tiwei Bie wrote:
> > This patch adaptively batches the small guest memory copies.
> > By batching the small copies, the efficiency of executing the
> > memory LOAD instructions can be improved greatly, because the
> > memory LOAD latency can be effectively hidden by the pipeline.
> > We saw great performance boosts for small packets PVP test.
> >
> > This patch improves the performance for small packets, and has
> > distinguished the packets by size. So although the performance
> > for big packets doesn't change, it makes it relatively easy to
> > do some special optimizations for the big packets too.
>
> Do you mean that if we would batch unconditionnaly whatever the size,
> we see performance drop for larger (>256) packets?
>
Yeah, you are right.
> Other question is about indirect descriptors, my understanding of the
> patch is that the number of batched copies is limited to the queue size.
> In theory, we could have more than that with indirect descriptors (first
> indirect desc for the vnet header, second one for the packet).
>
> So in the worst case, we would have the first small copies being
> batched, but not the last ones if there are more than queue size.
> So, I think it works, but I'd like your confirmation.
>
Yeah, you are right. If the number of small copies is larger than
the queue size, the last ones won't be batched any more.
> >
> > Signed-off-by: Tiwei Bie <tiwei.bie@intel.com>
> > Signed-off-by: Zhihong Wang <zhihong.wang@intel.com>
> > Signed-off-by: Zhiyong Yang <zhiyong.yang@intel.com>
> > ---
> > This optimization depends on the CPU internal pipeline design.
> > So further tests (e.g. ARM) from the community is appreciated.
>
> Agree, I think this is important to have it tested on ARM platforms at
> least to ensure it doesn't introduce a regression.
>
> Adding Santosh, Jerin & Hemant in cc, who might know who could do the
> test.
>
Thank you very much! :-)
Best regards,
Tiwei Bie
next prev parent reply other threads:[~2017-09-01 10:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 2:19 Tiwei Bie
2017-08-28 6:31 ` Jens Freimann
2017-08-28 11:41 ` Yao, Lei A
2017-09-01 9:45 ` Maxime Coquelin
2017-09-01 10:33 ` Tiwei Bie [this message]
2017-09-07 17:47 ` Maxime Coquelin
2017-09-08 0:48 ` Tiwei Bie
2017-09-08 7:41 ` Yuanhan Liu
2017-09-08 10:38 ` Tiwei Bie
2017-09-08 12:50 ` [dpdk-dev] [PATCH v2] " Tiwei Bie
2017-09-09 14:58 ` santosh
2017-09-11 1:27 ` Tiwei Bie
2017-09-11 12:06 ` Yuanhan 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=20170901103322.GA10109@debian-ZGViaWFuCg \
--to=tiwei.bie@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.com \
--cc=jerin.jacob@caviumnetworks.com \
--cc=maxime.coquelin@redhat.com \
--cc=santosh.shukla@caviumnetworks.com \
--cc=yliu@fridaylinux.org \
--cc=zhihong.wang@intel.com \
--cc=zhiyong.yang@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).