LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Xing Zhengjun <zhengjun.xing@linux.intel.com>
To: Trond Myklebust <trondmy@hammerspace.com>,
	"rong.a.chen@intel.com" <rong.a.chen@intel.com>
Cc: "lkp@01.org" <lkp@01.org>,
	"torvalds@linux-foundation.org" <torvalds@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [SUNRPC] 0472e47660: fsmark.app_overhead 16.0% regression
Date: Tue, 9 Jul 2019 10:39:20 +0800	[thread overview]
Message-ID: <e29f82e0-6847-b264-300b-130bb31399d1@linux.intel.com> (raw)
In-Reply-To: <DM5PR13MB1851813BBEA446E25C5001C2B8F60@DM5PR13MB1851.namprd13.prod.outlook.com>

Hi Trond,

On 7/8/2019 7:44 PM, Trond Myklebust wrote:
> I've asked several times now about how to interpret your results. As far 
> as I can tell from your numbers, the overhead appears to be entirely 
> contained in the NUMA section of your results.
> IOW: it would appear to be a scheduling overhead due to NUMA. I've been 
> asking whether or not that is a correct interpretation of the numbers 
> you published.
Thanks for your feedback. I used the same hardware and the same test 
parameters to test the two commits:
    e791f8e938 ("SUNRPC: Convert xs_send_kvec() to use iov_iter_kvec()")
    0472e47660 ("SUNRPC: Convert socket page send code to use iov_iter()")

If it is caused by NUMA, why only commit 0472e47660 throughput is 
decreased? The filesystem we test is NFS, commit 0472e47660 is related 
with the network, could you help to check if have any other clues for 
the regression. Thanks.

-- 
Zhengjun Xing

  parent reply	other threads:[~2019-07-09  2:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-20  5:54 kernel test robot
2019-05-30  1:35 ` [LKP] " Xing Zhengjun
2019-05-30  2:00   ` Trond Myklebust
2019-05-30  7:20     ` Xing Zhengjun
2019-05-30 19:10       ` Trond Myklebust
2019-05-31  3:27         ` Xing Zhengjun
2019-07-08  8:32           ` Xing Zhengjun
     [not found]             ` <DM5PR13MB1851813BBEA446E25C5001C2B8F60@DM5PR13MB1851.namprd13.prod.outlook.com>
2019-07-09  2:39               ` Xing Zhengjun [this message]
2019-07-12  6:42                 ` Xing Zhengjun
2019-07-24  5:17                   ` Xing Zhengjun
2019-08-07  7:56                     ` Xing Zhengjun
2019-08-30  0:43                       ` Xing Zhengjun
2019-09-25  9:00                         ` Xing Zhengjun

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=e29f82e0-6847-b264-300b-130bb31399d1@linux.intel.com \
    --to=zhengjun.xing@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=rong.a.chen@intel.com \
    --cc=torvalds@linux-foundation.org \
    --cc=trondmy@hammerspace.com \
    --subject='Re: [LKP] [SUNRPC] 0472e47660: fsmark.app_overhead 16.0% regression' \
    /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

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).