All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [fs] 3deb642f0d: will-it-scale.per_process_ops -8.8% regression
Date: Fri, 22 Jun 2018 17:02:51 +0200	[thread overview]
Message-ID: <20180622150251.GA12802@lst.de> (raw)
In-Reply-To: <20180622082752.GX11011@yexl-desktop>

[-- Attachment #1: Type: text/plain, Size: 243 bytes --]

Hi Xiaolong,

can you retest this workload on the following branch:

    git://git.infradead.org/users/hch/vfs.git remove-get-poll-head

Gitweb:

    http://git.infradead.org/users/hch/vfs.git/shortlog/refs/heads/remove-get-poll-head

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@lst.de>
To: kernel test robot <xiaolong.ye@intel.com>
Cc: Christoph Hellwig <hch@lst.de>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"Darrick J. Wong" <darrick.wong@oracle.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	lkp@01.org, viro@zeniv.linux.org.uk
Subject: Re: [lkp-robot] [fs]  3deb642f0d:  will-it-scale.per_process_ops -8.8% regression
Date: Fri, 22 Jun 2018 17:02:51 +0200	[thread overview]
Message-ID: <20180622150251.GA12802@lst.de> (raw)
In-Reply-To: <20180622082752.GX11011@yexl-desktop>

Hi Xiaolong,

can you retest this workload on the following branch:

    git://git.infradead.org/users/hch/vfs.git remove-get-poll-head

Gitweb:

    http://git.infradead.org/users/hch/vfs.git/shortlog/refs/heads/remove-get-poll-head

  parent reply	other threads:[~2018-06-22 15:02 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-22  8:27 [lkp-robot] [fs] 3deb642f0d: will-it-scale.per_process_ops -8.8% regression kernel test robot
2018-06-22  8:27 ` kernel test robot
2018-06-22  9:25 ` Linus Torvalds
2018-06-22  9:25   ` Linus Torvalds
2018-06-22  9:56   ` Christoph Hellwig
2018-06-22  9:56     ` Christoph Hellwig
2018-06-22 10:00     ` Christoph Hellwig
2018-06-22 10:00       ` Christoph Hellwig
2018-06-22 11:01       ` Al Viro
2018-06-22 11:01         ` Al Viro
2018-06-22 11:53         ` Christoph Hellwig
2018-06-22 11:53           ` Christoph Hellwig
2018-06-22 11:56           ` Al Viro
2018-06-22 11:56             ` Al Viro
2018-06-22 12:07             ` Christoph Hellwig
2018-06-22 12:07               ` Christoph Hellwig
2018-06-22 12:17               ` Al Viro
2018-06-22 12:17                 ` Al Viro
2018-06-22 12:33                 ` Christoph Hellwig
2018-06-22 12:33                   ` Christoph Hellwig
2018-06-22 12:29                   ` Al Viro
2018-06-22 12:29                     ` Al Viro
2018-06-22 19:06         ` Sean Paul
2018-06-22 19:06           ` Sean Paul
2018-06-22 10:02     ` Linus Torvalds
2018-06-22 10:02       ` Linus Torvalds
2018-06-22 10:05       ` Linus Torvalds
2018-06-22 10:05         ` Linus Torvalds
2018-06-22 15:02 ` Christoph Hellwig [this message]
2018-06-22 15:02   ` Christoph Hellwig
2018-06-22 15:14   ` Al Viro
2018-06-22 15:14     ` Al Viro
2018-06-22 15:28     ` Christoph Hellwig
2018-06-22 15:28       ` Christoph Hellwig
2018-06-22 16:18       ` Christoph Hellwig
2018-06-22 16:18         ` Christoph Hellwig
2018-06-22 20:02         ` Al Viro
2018-06-22 20:02           ` Al Viro
2018-06-23  7:15           ` Christoph Hellwig
2018-06-23  7:15             ` Christoph Hellwig
2018-06-26  6:03   ` Ye Xiaolong
2018-06-26  6:03     ` Ye Xiaolong
2018-06-27  7:07     ` Christoph Hellwig
2018-06-27  7:07       ` Christoph Hellwig
2018-06-28  0:38       ` Ye Xiaolong
2018-06-28  0:38         ` Ye Xiaolong
2018-06-28 13:38         ` Christoph Hellwig
2018-06-28 13:38           ` Christoph Hellwig

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=20180622150251.GA12802@lst.de \
    --to=hch@lst.de \
    --cc=lkp@lists.01.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.