DPDK patches and discussions
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: "Xia, Chenbo" <chenbo.xia@intel.com>, "Ding, Xuan" <xuan.ding@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Hu, Jiayu" <jiayu.hu@intel.com>,
	"He, Xingguang" <xingguang.he@intel.com>,
	"Yang, YvonneX" <yvonnex.yang@intel.com>,
	"Jiang, Cheng1" <cheng1.jiang@intel.com>
Subject: Re: [PATCH] vhost: fix unnecessary dirty page logging
Date: Thu, 7 Jul 2022 13:30:40 +0200	[thread overview]
Message-ID: <5f6441be-4ab3-7a0d-483d-432a8a519919@redhat.com> (raw)
In-Reply-To: <SN6PR11MB350487303FC5014CFED904F39C839@SN6PR11MB3504.namprd11.prod.outlook.com>



On 7/7/22 11:51, Xia, Chenbo wrote:
>> -----Original Message-----
>> From: Ding, Xuan <xuan.ding@intel.com>
>> Sent: Thursday, July 7, 2022 2:55 PM
>> To: maxime.coquelin@redhat.com; Xia, Chenbo <chenbo.xia@intel.com>
>> Cc: dev@dpdk.org; Hu, Jiayu <jiayu.hu@intel.com>; He, Xingguang
>> <xingguang.he@intel.com>; Yang, YvonneX <yvonnex.yang@intel.com>; Jiang,
>> Cheng1 <cheng1.jiang@intel.com>; Ding, Xuan <xuan.ding@intel.com>
>> Subject: [PATCH] vhost: fix unnecessary dirty page logging
>>
>> From: Xuan Ding <xuan.ding@intel.com>
>>
>> The dirty page logging is only required in vhost enqueue direction for
>> live migration. This patch removes the unnecessary dirty page logging
>> in vhost dequeue direction. Otherwise, it will result in a performance
>> drop. Some if-else judgements are also optimized to improve performance.
>>
>> Fixes: 6d823bb302c7 ("vhost: prepare sync for descriptor to mbuf
>> refactoring")
>> Fixes: b6eee3e83402 ("vhost: fix sync dequeue offload")
>>
>> Signed-off-by: Xuan Ding <xuan.ding@intel.com>
>> ---
> 
> Reviewed-by: Chenbo Xia <chenbo.xia@intel.com>
> 
> Although it's late in release, we can consider to merge this as I see it impacts
> the performance by 5%:
> http://inbox.dpdk.org/dev/BYAPR11MB2711F13CDA2B0A4535A6591EFE839@BYAPR11MB2711.namprd11.prod.outlook.com/T/#t

Yes, I raised we need it in -rc4 at today's Release status meeting.
I'll review it today.

> But also, it will be good to know the performance issue is solved by sharing the
> test results.

Yes, Intel performance results would be appreciated.

> Thanks,
> Chenbo
> 

Thanks,
Maxime


  reply	other threads:[~2022-07-07 11:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07  6:55 xuan.ding
2022-07-07  8:23 ` Hu, Jiayu
2022-07-07  9:51 ` Xia, Chenbo
2022-07-07 11:30   ` Maxime Coquelin [this message]
2022-07-08  7:04     ` Ding, Xuan
2022-07-08  7:53       ` He, Xingguang
2022-07-08  8:13         ` He, Xingguang
2022-07-08  7:57       ` Maxime Coquelin
2022-07-08  8:09         ` Ding, Xuan
2022-07-11  8:09           ` He, Xingguang
2022-07-07 12:04 ` Maxime Coquelin
2022-07-08  9:11 ` 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=5f6441be-4ab3-7a0d-483d-432a8a519919@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=chenbo.xia@intel.com \
    --cc=cheng1.jiang@intel.com \
    --cc=dev@dpdk.org \
    --cc=jiayu.hu@intel.com \
    --cc=xingguang.he@intel.com \
    --cc=xuan.ding@intel.com \
    --cc=yvonnex.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).