Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752617AbbLXNRM (ORCPT ); Thu, 24 Dec 2015 08:17:12 -0500 Received: from mail-wm0-f42.google.com ([74.125.82.42]:36674 "EHLO mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751949AbbLXNRK (ORCPT ); Thu, 24 Dec 2015 08:17:10 -0500 MIME-Version: 1.0 In-Reply-To: <87si2sbdky.fsf@yhuang-dev.intel.com> References: <87si2sbdky.fsf@yhuang-dev.intel.com> Date: Thu, 24 Dec 2015 05:17:08 -0800 Message-ID: Subject: Re: [net] ceb5d58b21: -69.2% fsmark.files_per_sec From: Eric Dumazet To: kernel test robot Cc: lkp@01.org, LKML , Dmitry Vyukov , "David S. Miller" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1313 Lines: 34 On Wed, Dec 23, 2015 at 9:49 PM, kernel test robot wrote: > FYI, we noticed the below changes on > > https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master > commit ceb5d58b217098a657f3850b7a2640f995032e62 ("net: fix sock_wake_async() rcu protection") > > > ========================================================================================= > compiler/cpufreq_governor/disk/filesize/fs2/fs/iterations/kconfig/nr_threads/rootfs/sync_method/tbox_group/test_size/testcase: > gcc-4.9/performance/1BRD_48G/4M/nfsv4/xfs/1x/x86_64-rhel/64t/debian-x86_64-2015-02-07.cgz/NoSync/lkp-hsx04/40G/fsmark > > commit: > 9cd3e072b0be17446e37d7414eac8a3499e0601e > ceb5d58b217098a657f3850b7a2640f995032e62 > > 9cd3e072b0be1744 ceb5d58b217098a657f3850b7a > ---------------- -------------------------- > %stddev %change %stddev > Thanks, > Ying Huang Hi Ying. I have no idea what these confusing numbers mean. Is your benchmark running faster (good thing) or slower (sorry, but we fixed a bug) Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/