.
Signed-off-by: Huang, Ying ying.hu...@intel.com
---
fs/f2fs/recovery.c |7 ---
1 file changed, 4 insertions(+), 3 deletions(-)
--- a/fs/f2fs/recovery.c
+++ b/fs/f2fs/recovery.c
@@ -172,8 +172,8 @@ static int find_fsync_dnodes(struct f2fs
if (IS_INODE(page
On Mon, 2014-09-08 at 22:23 -0700, Jaegeuk Kim wrote:
Hi Huang,
On Mon, Sep 08, 2014 at 07:38:26PM +0800, Huang Ying wrote:
For fsync, if the nid of a non-inode dnode nid of inode and the
inode is not checkpointed. The non-inode dnode may be written before
inode. So
On Mon, 2014-09-08 at 22:13 -0700, Jaegeuk Kim wrote:
Hi Huang,
On Mon, Sep 08, 2014 at 03:36:35PM +0800, huang ying wrote:
Hi, Jaegeuk,
On Mon, Sep 8, 2014 at 11:50 AM, Jaegeuk Kim jaeg...@kernel.org wrote:
Hi,
On Sun, Sep 07, 2014 at 11:38:30AM +0800, Huang Ying wrote
On Tue, 2014-09-09 at 00:41 -0700, Jaegeuk Kim wrote:
On Tue, Sep 09, 2014 at 01:43:46PM +0800, Huang Ying wrote:
On Mon, 2014-09-08 at 22:13 -0700, Jaegeuk Kim wrote:
Hi Huang,
On Mon, Sep 08, 2014 at 03:36:35PM +0800, huang ying wrote:
Hi, Jaegeuk,
On Mon, Sep 8, 2014
On Thu, 2014-09-11 at 22:13 -0700, Jaegeuk Kim wrote:
On Thu, Sep 11, 2014 at 08:25:17PM +0800, Huang Ying wrote:
On Wed, 2014-09-10 at 22:37 -0700, Jaegeuk Kim wrote:
On Wed, Sep 10, 2014 at 07:08:32PM +0800, huang ying wrote:
On Wed, Sep 10, 2014 at 3:21 PM, Jaegeuk Kim jaeg
The nm_i-fcnt checking is executed before spin_lock, so if another
thread delete the last free_nid from the list, the wrong nid may be
gotten. So fix the race condition by moving the nm_i-fnct checking
into spin_lock.
Signed-off-by: Huang, Ying ying.hu...@intel.com
---
fs/f2fs/node.h |6
Now, if there is no free nid in nm_i-free_nid_list, 0 may be saved
into next_free_nid of checkpoint, this may cause useless scanning for
next mount. nm_i-next_scan_nid should be a better default value than
0.
Signed-off-by: Huang, Ying ying.hu...@intel.com
---
fs/f2fs/checkpoint.c |3 ++-
1
On Fri, 2014-09-12 at 15:34 +0800, Huang Ying wrote:
On Thu, 2014-09-11 at 22:13 -0700, Jaegeuk Kim wrote:
On Thu, Sep 11, 2014 at 08:25:17PM +0800, Huang Ying wrote:
On Wed, 2014-09-10 at 22:37 -0700, Jaegeuk Kim wrote:
On Wed, Sep 10, 2014 at 07:08:32PM +0800, huang ying wrote
On Sun, 2014-09-14 at 00:38 -0700, Jaegeuk Kim wrote:
On Fri, Sep 12, 2014 at 03:34:48PM +0800, Huang Ying wrote:
On Thu, 2014-09-11 at 22:13 -0700, Jaegeuk Kim wrote:
On Thu, Sep 11, 2014 at 08:25:17PM +0800, Huang Ying wrote:
On Wed, 2014-09-10 at 22:37 -0700, Jaegeuk Kim wrote
On Sun, 2014-09-14 at 00:48 -0700, Jaegeuk Kim wrote:
On Sat, Sep 13, 2014 at 10:23:18PM +0800, Huang Ying wrote:
On Fri, 2014-09-12 at 15:34 +0800, Huang Ying wrote:
On Thu, 2014-09-11 at 22:13 -0700, Jaegeuk Kim wrote:
On Thu, Sep 11, 2014 at 08:25:17PM +0800, Huang Ying wrote
On Sat, 2014-09-20 at 09:23 -0700, Jaegeuk Kim wrote:
On Thu, Sep 18, 2014 at 09:04:11PM +0800, huang ying wrote:
On Thu, Sep 18, 2014 at 1:51 PM, Jaegeuk Kim jaeg...@kernel.org wrote:
We can summarize the roll forward recovery scenarios as follows.
[Term] F: fsync_mark, D
On Sat, 2014-09-20 at 20:36 -0700, Jaegeuk Kim wrote:
On Sun, Sep 21, 2014 at 07:22:32AM +0800, Huang Ying wrote:
On Sat, 2014-09-20 at 09:23 -0700, Jaegeuk Kim wrote:
On Thu, Sep 18, 2014 at 09:04:11PM +0800, huang ying wrote:
On Thu, Sep 18, 2014 at 1:51 PM, Jaegeuk Kim jaeg
...@lists.sourceforge.net
Cc: Jaegeuk Kim; Huang Ying
Subject: [f2fs-dev] [PATCH 2/3] f2fs: fix conditions to remain recovery
information in
f2fs_sync_file
This patch revisited whole the recovery information during the
f2fs_sync_file.
In this patch, there are three information to make a decision
On Wed, 2014-09-10 at 22:37 -0700, Jaegeuk Kim wrote:
On Wed, Sep 10, 2014 at 07:08:32PM +0800, huang ying wrote:
On Wed, Sep 10, 2014 at 3:21 PM, Jaegeuk Kim jaeg...@kernel.org wrote:
On Tue, Sep 09, 2014 at 07:31:49PM +0800, huang ying wrote:
On Tue, Sep 9, 2014 at 3:09 PM, Jaegeuk
On Thu, 2014-09-11 at 18:47 +0800, Chao Yu wrote:
-Original Message-
From: Jaegeuk Kim [mailto:jaeg...@kernel.org]
Sent: Thursday, September 11, 2014 1:37 PM
To: huang ying
Cc: linux-f2fs-de...@lists.sourceforge.net; LKML; Huang Ying
Subject: Re: [f2fs-dev] [PATCH] f2fs: Fix
estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: boot
default_monitors:
boottime:
kernel-size:
default_watchdogs
and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: will-it-scale
default_monitors:
wait: pre-test
uptime:
iostat:
vmstat:
numa-numastat:
numa
and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: boot
default_monitors:
boottime:
kernel-size:
default_watchdogs:
watch-oom:
watchdog:
cpufreq_governor:
model
FYI, similar information for 4a91ebc4ec70e83a2fbca622653da22bf8afda7b
too.
Best Regards,
Huang, Ying
On Tue, 2014-12-23 at 13:40 +0800, Huang Ying wrote:
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit
)
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: boot
default_monitors:
boottime:
kernel
On Tue, 2014-12-23 at 08:32 -0500, Steven Rostedt wrote:
On Tue, 23 Dec 2014 11:10:17 +0800
Huang Ying ying.hu...@intel.com wrote:
FYI, we noticed the below changes on
commit fef5a9e3717e7aea991a7ae9ff6a7a2d4c85 (ftrace: Replace
tramp_hash with old_*_hash to save space
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: will-it-scale
default_monitors:
wait: pre-test
uptime:
iostat:
vmstat:
numa-numastat:
numa-vmstat:
numa-meminfo:
proc-vmstat:
proc-stat:
meminfo:
slabinfo:
interrupts
FYI, we noticed the below changes on
After the commit, the file system failed to mount as in stderr file attached.
git://git.kernel.org/pub/scm/linux/kernel/git/tytso/ext4.git dev
commit fdfe073987619ec375da8d8a2701ab271d1b1339 (ext4: fix potential use after
free during resize)
FYI, we noticed the changes on
commit 40e7fcb19293cbdff02c74cb0668413480f82ea1 (ACPI: Add _DEP support to fix
battery issue on Asus T100TA)
The dmesg is as follow and attached.
[1.332908] ACPI: Power Resource [PG00] (on)
[1.341096] ACPI: Power Resource [PG01] (on)
[1.349277] ACPI:
FYI, we noticed the below changes on
commit 6098b45b32e6baeacc04790773ced9340601d511 (aio: block exit_aio() until
all context requests are completed)
testbox/testcase/testparams: vm-vp-2G/xfstests/4HDD-btrfs-generic-quick
2ff396be602f10b5 6098b45b32e6baeacc04790773
On Sun, 2014-12-14 at 17:03 -0800, Andy Lutomirski wrote:
On Sun, Dec 14, 2014 at 4:58 PM, Huang Ying ying.hu...@linux.intel.com
wrote:
FYI, we noticed the below changes on
commit 1ad83c858c7d4ea210429142c99a1548e6715a35 (x86_64,vsyscall: Make
vsyscall emulation configurable
FYI, we noticed the below changes on
commit 8b26ef98da3387eb57a8a5c1747c6e628948ee0c (f2fs: use rw_semaphore for
nat entry lock)
testbox/testcase/testparams:
lkp-ne04/fsmark/performance-1x-32t-1HDD-f2fs-8K-400M-fsyncBeforeClose-16d-256fpd
4634d71ed190c99e 8b26ef98da3387eb57a8a5c174
or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: thrulay
default_monitors:
wait: pre-test
uptime:
iostat:
vmstat:
numa-numastat:
numa-vmstat:
numa-meminfo:
proc-vmstat:
proc-stat:
meminfo:
slabinfo:
interrupts:
lock_stat
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git irq/urgent
commit c291ee622165cb2c8d4e7af63fffd499354a23be (genirq: Prevent proc race
against freeing of irq descriptors)
testbox/testcase/testparams:
On Mon, 2014-12-15 at 16:28 +0900, Joonsoo Kim wrote:
On Thu, Dec 11, 2014 at 04:00:30PM +0800, Huang Ying wrote:
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git master
commit 6a7d22008b2294f1dacbc77632a26f2142f2d4b0 (mm: Fix boot crash
analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: boot
boot-meminfo:
boot-slabinfo:
boot-memory:
memmap:
bootmem:
default_monitors:
boottime:
kernel
,
Huang, Ying
#
# Automatically generated file; DO NOT EDIT.
# Linux/i386 3.18.0-rc4 Kernel Configuration
#
# CONFIG_64BIT is not set
CONFIG_X86_32=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT=elf32-i386
CONFIG_ARCH_DEFCONFIG=arch/x86/configs/i386_defconfig
CONFIG_LOCKDEP_SUPPORT=y
On Thu, 2014-12-18 at 10:20 +0200, Oded Gabbay wrote:
On 12/18/2014 10:17 AM, Huang Ying wrote:
FYI, we noticed the below changes on
commit e28740ece34d314002b1ddfa14e8fb7c7b909489 (drm/radeon: Add radeon
-- amdkfd interface
estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: will-it-scale
default_monitors:
wait: pre-test
uptime:
iostat
On Thu, 2014-12-18 at 09:05 -0200, Mauro Carvalho Chehab wrote:
Hi Huang,
Em Thu, 18 Dec 2014 16:13:26 +0800
Huang Ying ying.hu...@intel.com escreveu:
FYI, we noticed the below changes on
commit 50d1bb93672fa2f42cec6e06ce799fbe864f57e9 (sb_edac: add support for
Haswell based
On Mon, 2014-12-15 at 11:31 -0600, Eric W. Biederman wrote:
Huang Ying ying.hu...@intel.com writes:
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git
for-testing
commit bbea5f5532501fdd67f46442ba7b1122d7ff3123
(userns
in this email
bin/run-local job.yaml
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase
/shm/kboot/pid-vm-vp-quantal-x86_64-58 -serial
file:/dev/shm/kboot/serial-vm-vp-quantal-x86_64-58 -daemonize -display none
-monitor null
Thanks,
Huang, Ying
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 3.17.0 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: will-it-scale
default-monitors:
wait: pre-test
uptime:
iostat:
vmstat:
numa-numastat:
numa-vmstat:
numa-meminfo:
proc-vmstat:
proc-stat:
meminfo
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: will-it-scale
default-monitors:
wait
bin/run-local job.yaml
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase
in the stderr after the commit
mount.nfs: an incorrect mount option was specified
Thanks,
Huang, Ying
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 3.19.0-rc4 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
tbench_srv
tbench 4 127.0.0.1
killall tbench_srv
___
LKP mailing list
l...@linux.intel.com
job.yaml
Description
FYI, we noticed the below changes on
commit 34b48db66e08ca1c1bc07cf305d672ac940268dc (block: remove artifical
max_hw_sectors cap)
testbox/testcase/testparams:
lkp-ws02/fileio/600s-100%-1HDD-btrfs-64G-1024f-seqrewr-sync
c2661b806092d8ea 34b48db66e08ca1c1bc07cf305
bin/run-local job.yaml
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase
difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: will-it-scale
default-monitors:
wait: pre-test
uptime:
iostat:
vmstat:
numa-numastat:
numa-vmstat:
numa-meminfo:
proc-vmstat:
proc-stat
-0x9fff)
Elapsed time: 20
Thanks,
Huang, Ying
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 3.16.0 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_OUTPUT_FORMAT=elf64-x86-64
CONFIG_ARCH_DEFCONFIG=arch/x86/configs
performance.
Thanks,
Huang, Ying
---
testcase: will-it-scale
default-monitors:
wait: pre-test
uptime:
iostat:
vmstat:
numa-numastat:
numa-vmstat:
numa-meminfo:
proc-vmstat:
proc-stat:
meminfo:
slabinfo:
interrupts:
lock_stat:
latency_stats:
softirqs
FYI, we noticed the below changes on
commit d9b7e4f717a167610a49ceb9e5969e80146c89a8 (ipmi: Periodically check to
see if irqs and messages are set right)
testbox/testcase/testparams: avoton3/idle/performance-10m
6a11e5c67a397e9a d9b7e4f717a167610a49ceb9e5
bin/run-local job.yaml
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: pigz
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/core
commit 6aa15f5a2febe058056180786bb39513ad5ae70d (mutex: In
mutex_spin_on_owner(), return true when owner changes)
testbox/testcase/testparams:
FYI, we noticed the below changes on
commit fb7332a9fedfd62b1ba6530c86f39f0fa38afd49 (mmu_gather: move minimal
range calculations into generic code)
testbox/testcase/testparams: ivb42/will-it-scale/performance-brk1
63648dd20fa0780a fb7332a9fedfd62b1ba6530c86
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/core
commit 871a6bb4916fef3123b6ff749b0dc82680fb0d2a (mutex: In
mutex_spin_on_owner(), return true when owner changes)
testbox/testcase/testparams:
Hi, Davidlohr,
Any update on this? The latest news I gotten is that you finally
reproduced this.
Best Regards,
Huang, Ying
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
,
Huang, Ying
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 3.19.0-rc5 Kernel Configuration
#
CONFIG_64BIT=y
CONFIG_X86_64=y
CONFIG_X86=y
CONFIG_INSTRUCTION_DECODER=y
CONFIG_PERF_EVENTS_INTEL_UNCORE=y
CONFIG_OUTPUT_FORMAT=elf64-x86-64
CONFIG_ARCH_DEFCONFIG=arch/x86/configs
Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: boot
default-monitors:
default_watchdogs:
watch-oom:
watchdog:
cpufreq_governor:
model: qemu
: 320M
Disclaimer:
Results have been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
On Thu, 2015-01-08 at 18:47 -0800, Davidlohr Bueso wrote:
On Thu, 2015-01-08 at 10:27 +0800, Huang Ying wrote:
FYI, we noticed the below changes on
commit c8c06efa8b552608493b7066c234cfa82c47fcea (mm: convert i_mmap_mutex
to rwsem)
testbox/testcase/testparams: lituya/unixbench
On Thu, 2015-01-08 at 14:43 +, David Vrabel wrote:
On 08/01/15 02:58, Huang Ying wrote:
FYI, we noticed the below changes on
commit 054954eb051f35e74b75a566a96fe756015352c8 (xen: switch to linear
virtual mapped sparse p2m list)
testbox/testcase/testparams: vm-kbuild-yocto-ia32
On Mon, 2015-01-05 at 09:06 -0500, Aristeu Rozanski wrote:
Hi,
On Fri, Dec 19, 2014 at 01:26:59PM +0800, Huang Ying wrote:
In fact, I am not complaining :-), just FYI. As I said, this may be a
expected behavior because this is a Haswell machine and the Haswell
support was added
...@twiddle.net, Ivan
Kokshaysky i...@jurassic.park.msu.ru, Matt Turner
matts...@gmail.com, Huang Ying ying.hu...@intel.com,
linux-kernel@vger.kernel.org, Paul McKenney paul...@linux.vnet.ibm.com,
David Howells dhowe...@redhat.com,
Pranith Kumar bobby.pr...@gmail.com, sta...@vger.kernel.org
|
+---+++
Best Regards,
Huang, Ying
On Mon, 2015-02-09 at 16:07 +0800, Huang Ying wrote:
FYI, we noticed the below changes on
commit 5ad6300524c0332ac67e912c20d6e5cf262ba58f (genetlink: disallow
subscribing to unknown mcast groups)
Although the frequency decreased a lot, from 100
On Wed, 2015-02-11 at 15:25 +0800, pang.xun...@zte.com.cn wrote:
Hello,
Does +1.1% unixbench.score mean better or worse?
Anyway, this is a load bug fix, does can affect the load balancing
behavior a little.
I think this means something better :)
Best Regards,
Huang, Ying
Regards
actual performance.
Thanks,
Huang, Ying
---
testcase: boot
default-monitors:
default_watchdogs:
watch-oom:
watchdog:
cpufreq_governor: performance
model: Westmere
memory: 2G
hdd_partitions: /dev/disk/by-id/ata-FUJITSU_MJA2250BH_G2_K95CT9C2G29W-part6
swap_partitions:
rootfs_partition: /dev
On Thu, 2015-02-05 at 13:41 +0800, Huang Ying wrote:
On Tue, 2015-02-03 at 10:27 +, Will Deacon wrote:
On Tue, Feb 03, 2015 at 07:45:04AM +, Huang Ying wrote:
FYI, we noticed the below changes on
commit 721c21c17ab958abf19a8fc611c3bd4743680e38 (mm: mmu_gather: use
tlb-end
FYI, we noticed the below changes on
commit c4a7ca774949960064dac11b326908f28407e8c3 (SUNRPC: Allow waiting on
memory allocation)
testbox/testcase/testparams:
nhm4/fsmark/performance-1x-32t-1HDD-f2fs-nfsv4-8K-400M-fsyncBeforeClose-16d-256fpd
127b21b89f9d8ba0 c4a7ca774949960064dac11b32
been estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: will-it-scale
default-monitors:
wait: pre-test
uptime
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: aim9
default-monitors:
wait: pre-test
uptime:
iostat:
vmstat:
numa-numastat:
numa-vmstat:
numa-meminfo:
proc
On Sun, 2015-02-15 at 13:02 -0500, Trond Myklebust wrote:
Hi guys,
On Sun, Feb 15, 2015 at 2:57 AM, Huang Ying ying.hu...@intel.com wrote:
FYI, we noticed the below changes on
commit c4a7ca774949960064dac11b326908f28407e8c3 (SUNRPC: Allow waiting on
memory allocation)
testbox
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 127b21b89f9d8ba0dc23e47b8c35d8a0bac9d6fc (SUNRPC: Adjust rpciod
workqueue parameters)
testbox/testcase/testparams:
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 10359213d05acf804558bda7cc9b8422a828d1cd (mm: incorporate read-only
pages into transparent huge pages)
testbox/testcase/testparams: xps2/pigz/performance-100%-512K
On Tue, 2015-02-03 at 10:27 +, Will Deacon wrote:
On Tue, Feb 03, 2015 at 07:45:04AM +, Huang Ying wrote:
FYI, we noticed the below changes on
commit 721c21c17ab958abf19a8fc611c3bd4743680e38 (mm: mmu_gather: use
tlb-end != 0 only for TLB invalidation)
Is this delta relative
Hi, Kirill,
Sorry for late.
On Tue, 2014-12-23 at 11:57 +0300, Kirill Tkhai wrote:
Hi, Huang,
what do these digits mean? What test does?
23.12.2014, 08:16, Huang Ying ying.hu...@intel.com:
FYI, we noticed the below changes on
commit a15b12ac36ad4e7b856a4ae54937ae26a51aebad (sched
estimated based on internal Intel analysis and are provided
for informational purposes only. Any difference in system hardware or software
design or configuration may affect actual performance.
Thanks,
Huang, Ying
---
testcase: netperf
default_monitors:
wait: pre-test
uptime:
iostat:
vmstat
On Wed, 2015-01-07 at 23:45 -0800, Davidlohr Bueso wrote:
On Thu, 2015-01-08 at 10:27 +0800, Huang Ying wrote:
Cc'ing Peter.
FYI, we noticed the below changes on
commit c8c06efa8b552608493b7066c234cfa82c47fcea (mm: convert i_mmap_mutex
to rwsem)
Same exact everything, except
++|
| |
O O O O O O O O O O O O O O O O O O O O O|
2e+06 +++
Thanks,
Huang, Ying
#
# Automatically generated file; DO NOT EDIT.
# Linux/x86_64 3.18.0-rc7 Kernel Configuration
On Wed, 2015-01-07 at 08:24 -0700, Jens Axboe wrote:
On 01/06/2015 07:33 PM, Huang Ying wrote:
FYI, we noticed the below changes on
commit f2298c0403b0dfcaef637eba0c02c4a06d7a25ab (null_blk: multi queue
aware block test driver)
testbox/testcase/testparams: vm-kbuild-yocto-i386/boot
On Thu, 2015-01-08 at 09:52 +0800, Ming Lei wrote:
On Thu, Jan 8, 2015 at 8:52 AM, Huang Ying ying.hu...@intel.com wrote:
On Wed, 2015-01-07 at 08:24 -0700, Jens Axboe wrote:
On 01/06/2015 07:33 PM, Huang Ying wrote:
FYI, we noticed the below changes on
commit
FYI, we noticed the below changes on
commit c8c06efa8b552608493b7066c234cfa82c47fcea (mm: convert i_mmap_mutex to
rwsem)
testbox/testcase/testparams: lituya/unixbench/performance-execl
83cde9e8ba95d180 c8c06efa8b552608493b7066c2
--
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git locking/urgent
commit ef9db2383c74a9cc0f7f4e0ec2740c865f6532d9 (lockdep: Fix module unload)
++--++
|
FYI, we noticed the below changes on
git://flatbed.openfabrics.org/~amirv/linux.git for-upstream
commit d7aa432ad5fa589c56a11bd7993cff05e9b87d05 (regression: Disable FENTRY
[topic: regression] [net-next:regression])
testbox/testcase/testparams: lkp-sb03/will-it-scale/poll2
5cd08c4aa1751f04
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 3a8b36f378060d20062a0918e99fae39ff077bf0 (Btrfs: fix data loss in the
fast fsync path)
testbox/testcase/testparams:
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/mst/vhost.git vhost-next
commit 38ada4d7c6b416b2c41e67b721ebcfeec89e4751 (pci: disable msi/msix at
probe time)
+--+++
|
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 07d2413a61db6500f58e614e873eed79d7f2ed72 (locking/mutex: In
mutex_spin_on_owner(), return true when owner changes)
testbox/testcase/testparams:
. It shows that boot will hang at
the same position.
BTW: the test is run on 32 bit system.
Best Regards,
Huang, Ying
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
On Wed, 2015-03-18 at 20:45 +0900, Tetsuo Handa wrote:
Huang Ying wrote:
On Tue, 2015-03-17 at 15:24 -0400, Johannes Weiner wrote:
On Tue, Mar 17, 2015 at 10:15:29AM -0700, Linus Torvalds wrote:
Explicitly adding the emails of other people involved with that commit
and the original
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit a92aac4f369eee8b410a94babc0b380159062f10 (Merge remote-tracking branch
'tip/auto-latest')
+--++++
| |
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git x86/entry
commit fbca3588d325bf1803ce0eecb35b27705f95ef7c (x86: Switch all C consumers
of kernel_stack to this_cpu_sp0)
+--+++
|
Sorry, please ignore this report, the commit is too old. I think that
should be fixed already.
Best Regards,
Huang, Ying
On Fri, 2015-03-13 at 11:02 +0800, Huang Ying wrote:
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit
Sorry for duplicated email. Forget to send to the patch author.
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit b3fd4f03ca0b9952221f39ae6790e698bf4b39e7 (locking/rwsem: Avoid
deceiving lock spinners)
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit b3fd4f03ca0b9952221f39ae6790e698bf4b39e7 (locking/rwsem: Avoid
deceiving lock spinners)
testbox/testcase/testparams:
brickland3/vm-scalability/performance-300s-small-allocs
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
commit 1a99367023f6ac664365a37fa508b059e31d0e88 (locking/rwsem: Check for
active lock before bailing on spinning)
There is some minor will-it-scale.per_thread_ops changes below (-1.8%),
FYI, we noticed the below changes on
git://flatbed.openfabrics.org/~amirv/linux.git for-upstream
commit ccd57b1bd32460d27bbb9c599e795628a3c66983 (rhashtable: Add immediate
rehash during insertion)
+-+++
|
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit a08a8cd375db9769588257e7782f6b6b68561b88 (NFS: Add attribute update
barriers to NFS writebacks)
testbox/testcase/testparams: ivb42/will-it-scale/performance-pthread_mutex2
() after this number of requests (0 - don't use
fsync()),
SB_ARG_TYPE_INT, 100},
I double checked that via a debug patch to sysbench too.
Best Regards,
Huang, Ying
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
is
called.
Huang Ying reported this to lkml after a test sysbench test that measured
a -62% decrease of file io requests for that tests' workload.
The test is:
echo performance /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo performance /sys/devices/system/cpu/cpu1
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit b191f9b106ea1a24a711dbebb2925d3313da5852 (mm: numa: preserve PTE write
permissions across a NUMA hinting fault)
testbox/testcase/testparams:
On Wed, 2015-03-25 at 10:54 +, Mel Gorman wrote:
On Mon, Mar 23, 2015 at 04:46:21PM +0800, Huang Ying wrote:
My attention is occupied by the automatic NUMA regression at the moment
but I haven't forgotten this. Even with the high client count, I was not
able to reproduce this so
On Thu, 2015-03-05 at 10:26 +, Mel Gorman wrote:
On Thu, Mar 05, 2015 at 01:34:59PM +0800, Huang Ying wrote:
Hi, Mel,
On Sat, 2015-02-28 at 15:30 +0800, Huang Ying wrote:
On Sat, 2015-02-28 at 01:46 +, Mel Gorman wrote:
On Fri, Feb 27, 2015 at 03:21:36PM +0800, Huang Ying
On Sat, 2015-02-28 at 01:46 +, Mel Gorman wrote:
On Fri, Feb 27, 2015 at 03:21:36PM +0800, Huang Ying wrote:
FYI, we noticed the below changes on
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
commit 3484b2de9499df23c4604a513b36f96326ae81ad (mm: rearrange
401 - 500 of 3349 matches
Mail list logo
