* 2.5.60-mm2
@ 2003-02-14 9:31 Andrew Morton
2003-02-14 9:38 ` 2.5.60-mm2 Dave Jones
2003-02-15 20:27 ` 2.5.60-mm2 Arador
0 siblings, 2 replies; 12+ messages in thread
From: Andrew Morton @ 2003-02-14 9:31 UTC (permalink / raw)
To: linux-kernel, linux-mm
http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.5/2.5.60/2.5.60-mm2/
. Robert has fixed up Ingo's scheduler update, so that's back in.
. Considerable poking at the NFS MAP_SHARED OOM lockup. It is limping
along now, but writeout bandwidth is poor and it is still struggling.
Needs work.
. There's a one-liner which removes an O(n^2) search in the NFS writeback
path. It increases writeout bandwidth by 4x and decreases CPU load from
100% to 3%. Needs work.
. A patch to permit direct-io reads of the partial block at EOF. Seems to
work, but needs more testing.
. There is another anticipatory scheduler patch over in experimental/.
The main obective of the anticipatory scheduler is not really to improve
interactivity. It is to increase throughput. Nick is showing some
impressive benchmark results with this now. Some benchmarking of the
non-contest variety would be appreciated.
. Added Matthew Jacob's Qlogic ISP driver for a bit of testing. It locks
up mysteriously with my ISP12160 controller. Testing results for other
controllers would be appreciated.
Changes since 2.5.60-mm1:
linus.patch
Latest bk from Linus
-genhd-warnings.patch
-vmscan-warning.patch
-nfsd-warnings.patch
-partitions-warnings.patch
-nfs-warning-fix.patch
-reiserfs-hashes-warning-fix.patch
-st-warning-fix.patch
-adaptec-compile-fix.patch
-adaptec-debug-fix.patch
-oprofile-p4.patch
-oprofile_cpu-as-string.patch
-oprofile-braino.patch
-disassociate_tty-fix.patch
-epoll-update-2.5.60.patch
-misc.patch
-dcache_rcu-nfs-server-fix.patch
-cyclone-fixes.patch
-enable-timer_cyclone.patch
-hugetlbfs-i_size-fix.patch
+jfs-build-fix.patch
JFS compile fix for gcc-2.95.3.
-mandlock-oops-fix.patch
+mandlock-fix.patch
Updated flocking fix
+fault_in_pages-move.patch
Move fault_in_pages_readable/writeable to a header file so reiserfs can
reuse it.
reiserfs_file_write.patch
Updated
+ext3-eio-fix.patch
Fix a BUG with fsx-linux
+smctr-fix.patch
compile fix.
+sched-f3.patch
+rml-scheduler-bits.patch
Updated scheduler update.
+nfs-speedup.patch
+nfs-more-oom-fix.patch
NFS OOM work.
+nfs-sendfile.patch
"fix" an O(n^2) problem in the NFS client.
+put_page-speedup.patch
Speed up put_page() for CONFIG_HUGETLB_PAGE=y
+kernel_lock_bug2.patch
+ext2_ext3_listxattr-bug.patch
+xattr-flags.patch
+xattr-flags-policy.patch
+xattr-trusted.patch
Extended attribute feature work.
+generic_write_checks.patch
Break out the bounds checking from generic_file_write() so other
filesystems can use them.
+balance_dirty_pages-lockup-fix.patch
Fix a weird lockup in the writeback code.
+cciss-1.patch
+cciss-2.patch
+cciss-3.patch
+cciss-5.patch
+cciss-6.patch
+cciss-7.patch
+cciss-8.patch
+cciss-9.patch
+cciss-10.patch
+cciss-11.patch
cciss array controller driver update
+direct-io-retval-fix.patch
Return the correct thing on -EIO
+dio-eof-read.patch
Allow direct-io reads of the non-aligned end of file.
+linux-isp.patch
Latest qlogic driver from www.feral.com bitkeeper
+linux-isp-update.patch
Port it to 2.5
In the experimental/ directory:
+handle-async-write-errors.patch
Framework for recording and reporting data loss during the async writeout
code.
+anticipatory_io_scheduling.patch
+ant-sched-9feb.patch
+ant-sched-12feb.patch
Anticipatory scheduler updates.
All 66 patches
linus.patch
kgdb.patch
ppc64-reloc_hide.patch
ppc64-time-warning.patch
kill ppc64 unused var warning
xfs-warning-fixes.patch
xfs-cli-fix.patch
xfs interrupt flags fix
ppc64-smp_prepare_cpus-warning.patch
ppc64: fix warning
report-lost-ticks.patch
make lost-tick detection more informative
devfs-fix.patch
ptrace-flush.patch
Subject: [PATCH] ptrace on 2.5.44
buffer-debug.patch
buffer.c debugging
warn-null-wakeup.patch
jfs-build-fix.patch
JFS build fix with gcc-2.95.3
ext3-truncate-ordered-pages.patch
ext3: explicitly free truncated pages
mandlock-fix.patch
Subject: [PATCH] Fix mandatory locking
fault_in_pages-move.patch
move fault_in_pages_readable/writeable to header
reiserfs_file_write.patch
Subject: reiserfs file_write patch
ext3-eio-fix.patch
fix ext3 BUG due to race with truncate
deadline-np-42.patch
(undescribed patch)
deadline-np-43.patch
(undescribed patch)
batch-tuning.patch
I/O scheduler tuning
starvation-by-read-fix.patch
fix starvation-by-readers in the IO scheduler
crc32-speedup.patch
crc32 improvements for 2.5
smctr-fix.patch
smctr.c build fixes
scheduler-tunables.patch
scheduler tunables
sched-f3.patch
scheduler F3-updated
rml-scheduler-bits.patch
scheduler bits
lockd-lockup-fix.patch
Subject: Re: Fw: Re: 2.4.20 NFS server lock-up (SMP)
rcu-stats.patch
RCU statistics reporting
dcache_rcu-fast_walk-revert.patch
dcache_rcu: revert fast_walk code
dcache_rcu-main.patch
dcache_rcu
smalldevfs.patch
smalldevfs
ext3-journalled-data-assertion-fix.patch
Remove incorrect assertion from ext3
deadline-hash-fix.patch
nfs-speedup.patch
nfs-oom-fix.patch
nfs oom fix
sk-allocation.patch
Subject: Re: nfs oom
nfs-more-oom-fix.patch
nfs-sendfile.patch
Implement sendfile() for NFS
rpciod-atomic-allocations.patch
Make rcpiod use atomic allocations
put_page-speedup.patch
hugetlb put_page speedup
kernel_lock_bug2.patch
ext2_ext3_listxattr-bug.patch
xattr: listxattr fix
xattr-flags.patch
xattr: infrastructure for permission overrides
xattr-flags-policy.patch
xattr: allow kernel code to override EA permissions
xattr-trusted.patch
xattr: trusted extended attributes
generic_write_checks.patch
separate checks from generic_file_aio_write
balance_dirty_pages-lockup-fix.patch
blk_congestion_wait tuning and lockup fix
cciss-1.patch
make cciss driver compile
cciss-2.patch
make cciss driver compile (2)
cciss-3.patch
make cciss driver compile [3]
cciss-5.patch
make cciss driver compile [5]
cciss-6.patch
make cciss driver compile [6]
cciss-7.patch
make cciss driver compile [7]
cciss-8.patch
make cciss driver compile
cciss-9.patch
make cciss driver compile
cciss-10.patch
make cciss driver compile
cciss-11.patch
make cciss driver compile
direct-io-retval-fix.patch
direct-io return value fix
dio-eof-read.patch
linux-isp.patch
linux-isp-update.patch
handle-async-write-errors.patch
Propagate async write errors to userspace
anticipatory_io_scheduling.patch
Subject: [PATCH] 2.5.59-mm3 antic io sched
ant-sched-9feb.patch
anticipatory scheduler fix
ant-sched-12feb.patch
Anticipatory scheduler tuning
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: 2.5.60-mm2
2003-02-14 9:31 2.5.60-mm2 Andrew Morton
@ 2003-02-14 9:38 ` Dave Jones
2003-02-14 9:58 ` 2.5.60-mm2 Andrew Morton
2003-02-14 10:10 ` 2.5.60-mm2 Thomas Schlichter
2003-02-15 20:27 ` 2.5.60-mm2 Arador
1 sibling, 2 replies; 12+ messages in thread
From: Dave Jones @ 2003-02-14 9:38 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
On Fri, Feb 14, 2003 at 01:31:44AM -0800, Andrew Morton wrote:
> . Considerable poking at the NFS MAP_SHARED OOM lockup. It is limping
> along now, but writeout bandwidth is poor and it is still struggling.
> Needs work.
>
> . There's a one-liner which removes an O(n^2) search in the NFS writeback
> path. It increases writeout bandwidth by 4x and decreases CPU load from
> 100% to 3%. Needs work.
I'm puzzled that you've had NFS stable enough to test these.
How much testing has this stuff had? Here 2.5.60+bk clients fall over under
moderate NFS load. (And go splat quickly under high load).
Trying to run things like dbench causes lockups, fsx/fstress made it
reboot, plus the odd 'cheating' errors reported yesterday.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
| SuSE Labs
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: 2.5.60-mm2
2003-02-14 9:38 ` 2.5.60-mm2 Dave Jones
@ 2003-02-14 9:58 ` Andrew Morton
2003-02-14 10:13 ` 2.5.60-mm2 Dave Jones
2003-02-14 10:10 ` 2.5.60-mm2 Thomas Schlichter
1 sibling, 1 reply; 12+ messages in thread
From: Andrew Morton @ 2003-02-14 9:58 UTC (permalink / raw)
To: Dave Jones; +Cc: linux-kernel, linux-mm
Dave Jones <davej@codemonkey.org.uk> wrote:
>
> On Fri, Feb 14, 2003 at 01:31:44AM -0800, Andrew Morton wrote:
>
> > . Considerable poking at the NFS MAP_SHARED OOM lockup. It is limping
> > along now, but writeout bandwidth is poor and it is still struggling.
> > Needs work.
> >
> > . There's a one-liner which removes an O(n^2) search in the NFS writeback
> > path. It increases writeout bandwidth by 4x and decreases CPU load from
> > 100% to 3%. Needs work.
>
> I'm puzzled that you've had NFS stable enough to test these.
This was just writing out a single 400 megabyte file with `dd'. I didn't try
anything fancier.
> How much testing has this stuff had? Here 2.5.60+bk clients fall over under
> moderate NFS load. (And go splat quickly under high load).
>
> Trying to run things like dbench causes lockups, fsx/fstress made it
> reboot, plus the odd 'cheating' errors reported yesterday.
I have not tried pushing NFS with complex access patterns recently.
BTW, there's a little patch in there from Trond which I forgot to mention: it
implements sendfile for NFS, so loop-on-NFS works again.
But we have a refcounting bug somewhere:
# mount server:/dir /mnt/point
# losetup /dev/loop0 /mnt/point/file
# mount /dev/loop0 /mnt/loop0
# umount /mnt/loop0
# losetup -d /dev/loop0
# umount /mnt/point
umount: /mnt/point: device is busy
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: 2.5.60-mm2
2003-02-14 9:38 ` 2.5.60-mm2 Dave Jones
2003-02-14 9:58 ` 2.5.60-mm2 Andrew Morton
@ 2003-02-14 10:10 ` Thomas Schlichter
2003-02-17 1:59 ` 2.5.60-mm2 Bill Davidsen
1 sibling, 1 reply; 12+ messages in thread
From: Thomas Schlichter @ 2003-02-14 10:10 UTC (permalink / raw)
To: Dave Jones, Andrew Morton; +Cc: linux-kernel, linux-mm
[-- Attachment #1: signed data --]
[-- Type: text/plain, Size: 1061 bytes --]
On Friday, 14. February 2003 10:38, Dave Jones wrote:
> On Fri, Feb 14, 2003 at 01:31:44AM -0800, Andrew Morton wrote:
> > . Considerable poking at the NFS MAP_SHARED OOM lockup. It is limping
> > along now, but writeout bandwidth is poor and it is still struggling.
> > Needs work.
> >
> > . There's a one-liner which removes an O(n^2) search in the NFS
> > writeback path. It increases writeout bandwidth by 4x and decreases CPU
> > load from 100% to 3%. Needs work.
>
> I'm puzzled that you've had NFS stable enough to test these.
> How much testing has this stuff had? Here 2.5.60+bk clients fall over under
> moderate NFS load. (And go splat quickly under high load).
>
> Trying to run things like dbench causes lockups, fsx/fstress made it
> reboot, plus the odd 'cheating' errors reported yesterday.
>
> Dave
I've got NFS problems with 2.5.5x - 60-bk3, too, but here I can workaround
them by simply pinging the NFS-server every second... Funny, but it works!
Perhaps this can help finding the real bug?!
Thomas
[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: 2.5.60-mm2
2003-02-14 9:58 ` 2.5.60-mm2 Andrew Morton
@ 2003-02-14 10:13 ` Dave Jones
2003-02-14 10:22 ` 2.5.60-mm2 Andrew Morton
0 siblings, 1 reply; 12+ messages in thread
From: Dave Jones @ 2003-02-14 10:13 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel, linux-mm
On Fri, Feb 14, 2003 at 01:58:02AM -0800, Andrew Morton wrote:
> > I'm puzzled that you've had NFS stable enough to test these.
> This was just writing out a single 400 megabyte file with `dd'. I didn't try
> anything fancier.
ok. Can you hold off pushing NFS bits to Linus until this gets
pinned down ? I really don't want to introduce any more variables
to this, especially when its so hard to pin down to an exact
replication scenario.
Trond thinks this could be not just NFS related but something
lurking deeper within net/ which could be even more annoying
to pin down, though I don't see any other odd network related
behaviour.
Dave
--
| Dave Jones. http://www.codemonkey.org.uk
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: 2.5.60-mm2
2003-02-14 10:13 ` 2.5.60-mm2 Dave Jones
@ 2003-02-14 10:22 ` Andrew Morton
0 siblings, 0 replies; 12+ messages in thread
From: Andrew Morton @ 2003-02-14 10:22 UTC (permalink / raw)
To: Dave Jones; +Cc: linux-kernel, linux-mm
Dave Jones <davej@codemonkey.org.uk> wrote:
>
> On Fri, Feb 14, 2003 at 01:58:02AM -0800, Andrew Morton wrote:
>
> > > I'm puzzled that you've had NFS stable enough to test these.
> > This was just writing out a single 400 megabyte file with `dd'. I didn't try
> > anything fancier.
>
> ok. Can you hold off pushing NFS bits to Linus until this gets
> pinned down ? I really don't want to introduce any more variables
> to this, especially when its so hard to pin down to an exact
> replication scenario.
I wouldn't push any NFS bits. It has a breathing maintainer ;)
I've been mainly looking at the OOM problems, which need MM help. Got
distracted.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: 2.5.60-mm2
@ 2003-02-14 13:02 Con Kolivas
0 siblings, 0 replies; 12+ messages in thread
From: Con Kolivas @ 2003-02-14 13:02 UTC (permalink / raw)
To: linux kernel mailing list; +Cc: Andrew Morton
[-- Attachment #1: Type: text/plain, Size: 4959 bytes --]
Got this on serial console while trying to boot 2.5.60-mm2:
bad: scheduling while atomic!
Call Trace:
[<c0112a41>] do_schedule+0x3d/0x2f4
[<c0112f45>] wait_for_completion+0x8d/0xd0
[<c0112d3c>] default_wake_function+0x0/0x1c
[<c0112d3c>] default_wake_function+0x0/0x1c
[<c01221a9>] create_workqueue+0x125/0x178
[<c010508e>] init+0x2a/0x17c
[<c0105064>] init+0x0/0x17c
[<c0106e5d>] kernel_thread_helper+0x5/0xc
aio_setup: sizeof(struct page) = 40
Journalled Block Device driver loaded
bad: scheduling while atomic!
Call Trace:
[<c0112a41>] do_schedule+0x3d/0x2f4
[<c0112f45>] wait_for_completion+0x8d/0xd0
[<c0112d3c>] default_wake_function+0x0/0x1c
[<c0112d3c>] default_wake_function+0x0/0x1c
[<c010508e>] init+0x2a/0x17c
[<c0105064>] init+0x0/0x17c
[<c0106e5d>] kernel_thread_helper+0x5/0xc
bad: scheduling while atomic!
Call Trace:
[<c0112a41>] do_schedule+0x3d/0x2f4
[<c0112f45>] wait_for_completion+0x8d/0xd0
[<c0112d3c>] default_wake_function+0x0/0x1c
[<c0112d3c>] default_wake_function+0x0/0x1c
[<c010508e>] init+0x2a/0x17c
[<c0105064>] init+0x0/0x17c
[<c0106e5d>] kernel_thread_helper+0x5/0xc
bad: scheduling while atomic!
Call Trace:
[<c0112a41>] do_schedule+0x3d/0x2f4
[<c0112f45>] wait_for_completion+0x8d/0xd0
[<c0112d3c>] default_wake_function+0x0/0x1c
[<c0112d3c>] default_wake_function+0x0/0x1c
[<c010508e>] init+0x2a/0x17c
[<c0105064>] init+0x0/0x17c
[<c0106e5d>] kernel_thread_helper+0x5/0xc
SGI XFS for Linux 2.5.60-mm2 with no debug enabled
bad: scheduling while atomic!
Call Trace:
[<c0112a41>] do_schedule+0x3d/0x2f4
[<c0112f45>] wait_for_completion+0x8d/0xd0
[<c0112d3c>] default_wake_function+0x0/0x1c
[<c0112d3c>] default_wake_function+0x0/0x1c
[<c01221a9>] create_workqueue+0x125/0x178
[<c021708f>] pagebuf_daemon_start+0xb/0x4c
[<c016180a>] create_proc_entry+0x9a/0xb4
[<c0151aeb>] register_filesystem+0x3b/0x70
[<c010508e>] init+0x2a/0x17c
[<c0105064>] init+0x0/0x17c
[<c0106e5d>] kernel_thread_helper+0x5/0xc
Serial: 8250/16550 driver $Revision: 1.90 $ IRQ sharing enabled
tts/0 at I/O 0x3f8 (irq = 4) is a 16550A
tts/1 at I/O 0x2f8 (irq = 3) is a 16550A
pty: 256 Unix98 ptys configured
Real Time Clock Driver v1.11
Non-volatile memory driver v1.2
Intel(R) PRO/100 Network Driver - version 2.1.29-k4
Copyright (c) 2002 Intel Corporation
PCI: Found IRQ 11 for device 00:04.0
bad: scheduling while atomic!
Call Trace:
[<c0112a41>] do_schedule+0x3d/0x2f4
[<c011b907>] add_timer+0x11b/0x120
[<c011c478>] schedule_timeout+0x84/0xac
[<c011c3e8>] process_timeout+0x0/0xc
[<c024d974>] e100_selftest+0x58/0xb0
[<c02297f9>] pci_device_probe+0x41/0x5c
[<c02302d3>] bus_match+0x37/0x60
[<c0230394>] driver_attach+0x3c/0x5c
[<c0230622>] bus_add_driver+0xa6/0xd8
[<c023095c>] driver_register+0x34/0x38
[<c02298f2>] pci_register_driver+0x42/0x54
[<c010508e>] init+0x2a/0x17c
[<c0105064>] init+0x0/0x17c
[<c0106e5d>] kernel_thread_helper+0x5/0xc
bad: scheduling while atomic!
Call Trace:
[<c0112a41>] do_schedule+0x3d/0x2f4
[<c011b907>] add_timer+0x11b/0x120
[<c011c478>] schedule_timeout+0x84/0xac
[<c011c3e8>] process_timeout+0x0/0xc
[<c02297f9>] pci_device_probe+0x41/0x5c
[<c02302d3>] bus_match+0x37/0x60
[<c0230394>] driver_attach+0x3c/0x5c
[<c0230622>] bus_add_driver+0xa6/0xd8
[<c023095c>] driver_register+0x34/0x38
[<c02298f2>] pci_register_driver+0x42/0x54
[<c010508e>] init+0x2a/0x17c
[<c0105064>] init+0x0/0x17c
[<c0106e5d>] kernel_thread_helper+0x5/0xc
Freeing alive device c13a8000, eth%d
alloc_skb called nonatomically from interrupt c027978c
------------[ cut here ]------------
kernel BUG at net/core/skbuff.c:178!
invalid operand: 0000
CPU: 0
EIP: 0060:[<c0270863>] Not tainted
EFLAGS: 00010246
EIP is at alloc_skb+0x43/0x1a4
eax: 0000003a ebx: c0389b60 ecx: c02f4188 edx: 00000296
esi: c13a8000 edi: 000000d0 ebp: c13a8000 esp: c129feac
ds: 007b es: 007b ss: 0068
Process swapper (pid: 1, threadinfo=c129e000 task=c129c040)
Stack: c02e9740 c027978c c0389b60 c13a8000 00000005 c027978c 00000f60 000000d0
c0389b60 c0279c3e 00000010 c13a8000 ffffffff c011f98a c0389b60 00000005
c13a8000 c129e000 c03876a1 c03876c8 c02754b0 c040ee64 00000005 c13a8000
Call Trace:
[<c027978c>] rtmsg_ifinfo+0x10/0x78
[<c027978c>] rtmsg_ifinfo+0x10/0x78
[<c0279c3e>] rtnetlink_event+0x36/0x3c
[<c011f98a>] notifier_call_chain+0x1e/0x38
[<c02754b0>] register_netdevice+0x168/0x174
[<c0254c3e>] register_netdev+0x5e/0x70
[<c02297f9>] pci_device_probe+0x41/0x5c
[<c02302d3>] bus_match+0x37/0x60
[<c0230394>] driver_attach+0x3c/0x5c
[<c0230622>] bus_add_driver+0xa6/0xd8
[<c023095c>] driver_register+0x34/0x38
[<c02298f2>] pci_register_driver+0x42/0x54
[<c010508e>] init+0x2a/0x17c
[<c0105064>] init+0x0/0x17c
[<c0106e5d>] kernel_thread_helper+0x5/0xc
Code: 0f 0b b2 00 e3 96 2e c0 83 c4 08 83 e7 ef 31 c0 9c 59 fa be
<0>Kernel panic: Aiee, killing interrupt handler!
In interrupt handler - not syncing
.config attached
Con
[-- Attachment #2: osdl.config --]
[-- Type: text/plain, Size: 13139 bytes --]
#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_SWAP=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
#
# General setup
#
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
#
# Loadable module support
#
# CONFIG_MODULES is not set
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_TSC=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
CONFIG_X86_PREFETCH=y
# CONFIG_HUGETLB_PAGE is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
# CONFIG_X86_UP_APIC is not set
# CONFIG_X86_MCE is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y
#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set
#
# ACPI Support
#
# CONFIG_ACPI is not set
# CONFIG_CPU_FREQ is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
# CONFIG_SCx200 is not set
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_HOTPLUG is not set
#
# Executable file formats
#
CONFIG_KCORE_ELF=y
# CONFIG_KCORE_AOUT is not set
CONFIG_BINFMT_AOUT=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
# CONFIG_PARPORT is not set
#
# Plug and Play support
#
# CONFIG_PNP is not set
#
# Block devices
#
# CONFIG_BLK_DEV_FD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_LOOP is not set
CONFIG_BLK_DEV_NBD=y
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_LBD is not set
#
# ATA/ATAPI/MFM/RLL device support
#
CONFIG_IDE=y
#
# IDE, ATA and ATAPI Block devices
#
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
# CONFIG_BLK_DEV_HD is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
# CONFIG_BLK_DEV_IDECD is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_IDE_TASK_IOCTL is not set
#
# IDE chipset support/bugfixes
#
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_BLK_DEV_GENERIC=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDE_TCQ is not set
CONFIG_BLK_DEV_OFFBOARD=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_PCI_WIP=y
# CONFIG_IDEDMA_NEW_DRIVE_LISTINGS is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_SVWKS=y
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
CONFIG_IDEDMA_AUTO=y
CONFIG_IDEDMA_IVB=y
CONFIG_BLK_DEV_IDE_MODES=y
#
# SCSI device support
#
# CONFIG_SCSI is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
#
# Fusion MPT device support
#
#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_NETLINK_DEV=y
# CONFIG_NETFILTER is not set
# CONFIG_FILTER is not set
CONFIG_UNIX=y
CONFIG_NET_KEY=y
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
CONFIG_INET_ECN=y
# CONFIG_SYN_COOKIES is not set
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_XFRM_USER is not set
# CONFIG_IPV6 is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=y
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_ETHERTAP is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_MII is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_DGRS is not set
CONFIG_EEPRO100=y
CONFIG_E100=y
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
# CONFIG_NE2K_PCI is not set
# CONFIG_8139CP is not set
# CONFIG_8139TOO is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
CONFIG_SLIP=y
CONFIG_SLIP_COMPRESSED=y
CONFIG_SLIP_SMART=y
CONFIG_SLIP_MODE_SLIP6=y
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# Token Ring devices (depends on LLC=y)
#
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set
#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set
#
# ISDN subsystem
#
# CONFIG_ISDN_BOOL is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
# CONFIG_INPUT_MOUSEDEV is not set
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set
#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
# CONFIG_INPUT_MOUSE is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
# CONFIG_INPUT_PCSPKR is not set
# CONFIG_INPUT_UINPUT is not set
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_UNIX98_PTY_COUNT=256
#
# I2C support
#
# CONFIG_I2C is not set
#
# I2C Hardware Sensors Mainboard support
#
#
# I2C Hardware Sensors Chip support
#
#
# Mice
#
# CONFIG_BUSMOUSE is not set
# CONFIG_QIC02_TAPE is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_INTEL_RNG is not set
# CONFIG_AMD_RNG is not set
CONFIG_NVRAM=y
CONFIG_RTC=y
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
# CONFIG_AGP is not set
# CONFIG_DRM is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# File systems
#
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
CONFIG_REISERFS_FS=y
# CONFIG_REISERFS_CHECK is not set
CONFIG_REISERFS_PROC_INFO=y
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_FAT_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
CONFIG_TMPFS=y
CONFIG_RAMFS=y
# CONFIG_ISO9660_FS is not set
CONFIG_JFS_FS=y
# CONFIG_JFS_POSIX_ACL is not set
# CONFIG_JFS_DEBUG is not set
CONFIG_JFS_STATISTICS=y
# CONFIG_MINIX_FS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_NTFS_FS is not set
# CONFIG_HPFS_FS is not set
CONFIG_PROC_FS=y
CONFIG_DEVFS_FS=y
# CONFIG_DEVFS_MOUNT is not set
# CONFIG_DEVFS_DEBUG is not set
CONFIG_DEVPTS_FS=y
# CONFIG_QNX4FS_FS is not set
# CONFIG_ROMFS_FS is not set
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UDF_FS is not set
# CONFIG_UFS_FS is not set
CONFIG_XFS_FS=y
# CONFIG_XFS_RT is not set
# CONFIG_XFS_QUOTA is not set
# CONFIG_XFS_POSIX_ACL is not set
#
# Network File Systems
#
# CONFIG_CODA_FS is not set
# CONFIG_INTERMEZZO_FS is not set
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
# CONFIG_CIFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_NCP_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
#
# Native Language Support
#
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_737=y
CONFIG_NLS_CODEPAGE_775=y
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_CODEPAGE_852=y
CONFIG_NLS_CODEPAGE_855=y
CONFIG_NLS_CODEPAGE_857=y
CONFIG_NLS_CODEPAGE_860=y
CONFIG_NLS_CODEPAGE_861=y
CONFIG_NLS_CODEPAGE_862=y
CONFIG_NLS_CODEPAGE_863=y
CONFIG_NLS_CODEPAGE_864=y
CONFIG_NLS_CODEPAGE_865=y
CONFIG_NLS_CODEPAGE_866=y
CONFIG_NLS_CODEPAGE_869=y
CONFIG_NLS_CODEPAGE_936=y
CONFIG_NLS_CODEPAGE_950=y
CONFIG_NLS_CODEPAGE_932=y
CONFIG_NLS_CODEPAGE_949=y
CONFIG_NLS_CODEPAGE_874=y
CONFIG_NLS_ISO8859_8=y
CONFIG_NLS_CODEPAGE_1250=y
CONFIG_NLS_CODEPAGE_1251=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_ISO8859_2=y
CONFIG_NLS_ISO8859_3=y
CONFIG_NLS_ISO8859_4=y
CONFIG_NLS_ISO8859_5=y
CONFIG_NLS_ISO8859_6=y
CONFIG_NLS_ISO8859_7=y
CONFIG_NLS_ISO8859_9=y
CONFIG_NLS_ISO8859_13=y
CONFIG_NLS_ISO8859_14=y
CONFIG_NLS_ISO8859_15=y
CONFIG_NLS_KOI8_R=y
CONFIG_NLS_KOI8_U=y
CONFIG_NLS_UTF8=y
#
# Graphics support
#
# CONFIG_FB is not set
CONFIG_VIDEO_SELECT=y
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y
#
# Sound
#
# CONFIG_SOUND is not set
#
# USB support
#
# CONFIG_USB is not set
#
# Bluetooth support
#
# CONFIG_BT is not set
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_X86_REMOTE_DEBUG is not set
# CONFIG_DEBUG_IOVIRT is not set
CONFIG_MAGIC_SYSRQ=y
# CONFIG_DEBUG_SPINLOCK is not set
CONFIG_KALLSYMS=y
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set
#
# Security options
#
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Library routines
#
# CONFIG_CRC32 is not set
CONFIG_X86_BIOS_REBOOT=y
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: 2.5.60-mm2
2003-02-14 9:31 2.5.60-mm2 Andrew Morton
2003-02-14 9:38 ` 2.5.60-mm2 Dave Jones
@ 2003-02-15 20:27 ` Arador
1 sibling, 0 replies; 12+ messages in thread
From: Arador @ 2003-02-15 20:27 UTC (permalink / raw)
To: Andrew Morton; +Cc: piggin, linux-kernel, linux-mm
On Fri, 14 Feb 2003 01:31:44 -0800
Andrew Morton <akpm@digeo.com> wrote:
> The main obective of the anticipatory scheduler is not really to improve
> interactivity. It is to increase throughput. Nick is showing some
> impressive benchmark results with this now. Some benchmarking of the
> non-contest variety would be appreciated.
[...]
> anticipatory_io_scheduling.patch
> Subject: [PATCH] 2.5.59-mm3 antic io sched
>
> ant-sched-9feb.patch
> anticipatory scheduler fix
>
> ant-sched-12feb.patch
> Anticipatory scheduler tuning
(I applied those three)
Those are tiobench's results:
in both:
No size specified, using 510 MB
Unit information
================
File size = megabytes
Blk Size = bytes
Rate = megabytes per second
CPU% = percentage of CPU used during the test
Latency = milliseconds
Lat% = percent of requests that took longer than X seconds
CPU Eff = Rate divided by CPU% - throughput per cpu load
diff between both
Sequential reads
File Blk Num Avg Maximum Lat% Lat% CPU
Identifier Size Size Thr Rate (CPU%) Latency Latency >2s >10s Eff
---------------------------- ------ ----- --- ------ ------ --------- ----------- -------- -------- -----
-2.5.60-mm2 510 4096 1 21.23 8.264% 0.183 111.66 0.00000 0.00000 257
-2.5.60-mm2 510 4096 2 7.33 3.506% 1.061 196.42 0.00000 0.00000 209
-2.5.60-mm2 510 4096 4 5.39 2.593% 2.874 275.79 0.00000 0.00000 208
-2.5.60-mm2 510 4096 8 4.45 2.125% 6.846 1008.67 0.00000 0.00000 209
+2.5.60-mm2-ant 510 4096 1 42.07 17.81% 0.092 57.22 0.00000 0.00000 236
+2.5.60-mm2-ant 510 4096 2 22.84 12.08% 0.332 308.44 0.00000 0.00000 189
+2.5.60-mm2-ant 510 4096 4 17.40 9.298% 0.873 695.78 0.00000 0.00000 187
+2.5.60-mm2-ant 510 4096 8 11.62 6.064% 2.484 1334.89 0.00000 0.00000 192
Random Reads
File Blk Num Avg Maximum Lat% Lat% CPU
Identifier Size Size Thr Rate (CPU%) Latency Latency >2s >10s Eff
---------------------------- ------ ----- --- ------ ------ --------- ----------- -------- -------- -----
-2.5.60-mm2 510 4096 1 0.75 0.775% 5.190 57.26 0.00000 0.00000 97
-2.5.60-mm2 510 4096 2 0.62 0.611% 12.433 122.61 0.00000 0.00000 102
-2.5.60-mm2 510 4096 4 0.54 0.524% 28.542 534.94 0.00000 0.00000 102
-2.5.60-mm2 510 4096 8 0.49 0.527% 58.520 941.25 0.00000 0.00000 94
+2.5.60-mm2-ant 510 4096 1 0.71 0.742% 5.522 62.66 0.00000 0.00000 95
+2.5.60-mm2-ant 510 4096 2 0.63 0.574% 12.137 274.13 0.00000 0.00000 109
+2.5.60-mm2-ant 510 4096 4 0.58 0.548% 24.428 282.18 0.00000 0.00000 106
+2.5.60-mm2-ant 510 4096 8 0.63 0.549% 41.976 596.08 0.00000 0.00000 115
Sequential Writes
File Blk Num Avg Maximum Lat% Lat% CPU
Identifier Size Size Thr Rate (CPU%) Latency Latency >2s >10s Eff
---------------------------- ------ ----- --- ------ ------ --------- ----------- -------- -------- -----
-2.5.60-mm2 510 4096 1 26.59 38.97% 0.119 559.77 0.00000 0.00000 68
-2.5.60-mm2 510 4096 2 16.14 29.96% 0.390 6813.03 0.00306 0.00000 54
-2.5.60-mm2 510 4096 4 9.55 18.37% 1.249 16573.28 0.01615 0.00154 52
-2.5.60-mm2 510 4096 8 6.35 11.40% 4.342 45796.21 0.02093 0.01550 56
+2.5.60-mm2-ant 510 4096 1 33.87 49.55% 0.093 370.18 0.00000 0.00000 68
+2.5.60-mm2-ant 510 4096 2 12.56 24.08% 0.531 9524.84 0.00613 0.00000 52
+2.5.60-mm2-ant 510 4096 4 6.68 13.08% 2.071 20422.31 0.03153 0.00231 51
+2.5.60-mm2-ant 510 4096 8 6.90 13.45% 3.086 41464.78 0.02790 0.01163 51
Random Writes
File Blk Num Avg Maximum Lat% Lat% CPU
Identifier Size Size Thr Rate (CPU%) Latency Latency >2s >10s Eff
---------------------------- ------ ----- --- ------ ------ --------- ----------- -------- -------- -----
-2.5.60-mm2 510 4096 1 0.99 1.050% 0.140 33.67 0.00000 0.00000 95
-2.5.60-mm2 510 4096 2 1.02 1.138% 0.043 11.72 0.00000 0.00000 90
-2.5.60-mm2 510 4096 4 1.02 1.423% 0.082 99.74 0.00000 0.00000 72
-2.5.60-mm2 510 4096 8 0.99 1.329% 0.074 74.51 0.00000 0.00000 74
+2.5.60-mm2-ant 510 4096 1 0.96 0.917% 0.027 1.03 0.00000 0.00000 105
+2.5.60-mm2-ant 510 4096 2 1.00 1.472% 0.044 2.42 0.00000 0.00000 68
+2.5.60-mm2-ant 510 4096 4 0.95 1.367% 0.044 1.96 0.00000 0.00000 69
+2.5.60-mm2-ant 510 4096 8 0.99 1.431% 0.079 75.46 0.00000 0.00000 69
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: 2.5.60-mm2
2003-02-14 10:10 ` 2.5.60-mm2 Thomas Schlichter
@ 2003-02-17 1:59 ` Bill Davidsen
2003-02-17 12:08 ` 2.5.60-mm2 Bill Davidsen
0 siblings, 1 reply; 12+ messages in thread
From: Bill Davidsen @ 2003-02-17 1:59 UTC (permalink / raw)
To: Thomas Schlichter; +Cc: Dave Jones, Andrew Morton, linux-kernel, linux-mm
[-- Attachment #1: signed data --]
[-- Type: TEXT/PLAIN, Size: 552 bytes --]
On Fri, 14 Feb 2003, Thomas Schlichter wrote:
> I've got NFS problems with 2.5.5x - 60-bk3, too, but here I can workaround
> them by simply pinging the NFS-server every second... Funny, but it works!
> Perhaps this can help finding the real bug?!
I was looking for network issues when I started timing pings, and didn't
see any. I thought it was bad timing, link not raining when you have a
coat, but maybe I was curing it.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
[-- Attachment #2: signature --]
[-- Type: APPLICATION/PGP-SIGNATURE, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: 2.5.60-mm2
2003-02-17 1:59 ` 2.5.60-mm2 Bill Davidsen
@ 2003-02-17 12:08 ` Bill Davidsen
2003-02-17 12:35 ` 2.5.60-mm2 Thomas Schlichter
0 siblings, 1 reply; 12+ messages in thread
From: Bill Davidsen @ 2003-02-17 12:08 UTC (permalink / raw)
To: Thomas Schlichter; +Cc: Linux Kernel Mailing List, linux-mm
[-- Attachment #1: signed data --]
[-- Type: TEXT/PLAIN, Size: 954 bytes --]
On Sun, 16 Feb 2003, I wrote:
> > I've got NFS problems with 2.5.5x - 60-bk3, too, but here I can workaround
> > them by simply pinging the NFS-server every second... Funny, but it works!
> > Perhaps this can help finding the real bug?!
[ let's try this again, not typing in a moving car ]
> I was looking for network issues when I started timing pings, and didn't
> see any. I thought it was bad timing, like not raining when you have a
> coat, but maybe I was curing it.
Since it's possible that pings will actually change the problem rather
than measure it, I'll tcpdump for a while and see if that tells me
anything. I suspected network problems, since tcp has priority over udp in
some places.
I looked at the code last night, but I don't see anything explaining a
ping making things better. Something getting flushed?
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
[-- Attachment #2: signature --]
[-- Type: APPLICATION/PGP-SIGNATURE, Size: 189 bytes --]
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: 2.5.60-mm2
2003-02-17 12:08 ` 2.5.60-mm2 Bill Davidsen
@ 2003-02-17 12:35 ` Thomas Schlichter
2003-02-17 18:32 ` 2.5.60-mm2 Bill Davidsen
0 siblings, 1 reply; 12+ messages in thread
From: Thomas Schlichter @ 2003-02-17 12:35 UTC (permalink / raw)
To: Bill Davidsen; +Cc: Linux Kernel Mailing List, linux-mm
Quoting Bill Davidsen <davidsen@tmr.com>:
> On Sun, 16 Feb 2003, I wrote:
>
> > > I've got NFS problems with 2.5.5x - 60-bk3, too, but here I can
> workaround
> > > them by simply pinging the NFS-server every second... Funny, but it
> works!
> > > Perhaps this can help finding the real bug?!
>
> [ let's try this again, not typing in a moving car ]
>
> > I was looking for network issues when I started timing pings, and didn't
> > see any. I thought it was bad timing, like not raining when you have a
> > coat, but maybe I was curing it.
>
> Since it's possible that pings will actually change the problem rather
> than measure it, I'll tcpdump for a while and see if that tells me
> anything. I suspected network problems, since tcp has priority over udp in
> some places.
>
> I looked at the code last night, but I don't see anything explaining a
> ping making things better. Something getting flushed?
I'm sorry, I don't exactly know what you want me to do... I'm not involved in
the linux net code and I did not even try to understand it yet...
I just have a small environment with a FreeBSD 4.6 box using my Linux box as a
NFS file server. This worked fine with my 2.4 kernel but with the 2.5.x test
kernels I've got the problem the FreeBSD box says 'NFS server not responding'
until I do simple pings (ICMP echo request, ICMP echo respond) to the linux box
(the NFS server)...
Letting the ping run all the time NFS works so stable I even can do lots of
compilations over it without any problems.
So I don't have any answer WHY this helps, but it does... Perhaps it really is
just a timing issue, I just don't know... If you can tell me what to measure and
which values would be interesting I'll do these tests and send you the
results...
Thomas Schlichter
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: 2.5.60-mm2
2003-02-17 12:35 ` 2.5.60-mm2 Thomas Schlichter
@ 2003-02-17 18:32 ` Bill Davidsen
0 siblings, 0 replies; 12+ messages in thread
From: Bill Davidsen @ 2003-02-17 18:32 UTC (permalink / raw)
To: Thomas Schlichter; +Cc: Linux Kernel Mailing List, linux-mm
On Mon, 17 Feb 2003, Thomas Schlichter wrote:
> Quoting Bill Davidsen <davidsen@tmr.com>:
> > > I was looking for network issues when I started timing pings, and didn't
> > > see any. I thought it was bad timing, like not raining when you have a
> > > coat, but maybe I was curing it.
> >
> > Since it's possible that pings will actually change the problem rather
> > than measure it, I'll tcpdump for a while and see if that tells me
> > anything. I suspected network problems, since tcp has priority over udp in
> > some places.
> >
> > I looked at the code last night, but I don't see anything explaining a
> > ping making things better. Something getting flushed?
>
> I'm sorry, I don't exactly know what you want me to do... I'm not involved in
> the linux net code and I did not even try to understand it yet...
Thanks, you've already done it! I assumed that when I didn't see any
problems while the ping was running that it was just bad timing, and the
problem didn't happen while I was looking. Your note that the pinging
actually prevents the problem gives me something new to investigate.
> I just have a small environment with a FreeBSD 4.6 box using my Linux box as a
> NFS file server. This worked fine with my 2.4 kernel but with the 2.5.x test
> kernels I've got the problem the FreeBSD box says 'NFS server not responding'
> until I do simple pings (ICMP echo request, ICMP echo respond) to the linux box
> (the NFS server)...
>
> Letting the ping run all the time NFS works so stable I even can do lots of
> compilations over it without any problems.
>
> So I don't have any answer WHY this helps, but it does... Perhaps it really is
> just a timing issue, I just don't know... If you can tell me what to measure and
> which values would be interesting I'll do these tests and send you the
> results...
I someone can suggest "what to do" I'll do it as well. At the moment I'm
building a table of 2.5.59 client against 2.4.19, AIX, BSD, etc, and vice
versa. I am looking for hangs with and without the ping running, in hopes
that the results will be useful, possibly to me but more likely to someone
who can see what's happening.
For the record, I see severe hangs with 2.4.19 server and 2.5.59 client,
I'll know what effect the ping has in a few minutes.
--
bill davidsen <davidsen@tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2003-02-17 18:25 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-02-14 13:02 2.5.60-mm2 Con Kolivas
-- strict thread matches above, loose matches on Subject: below --
2003-02-14 9:31 2.5.60-mm2 Andrew Morton
2003-02-14 9:38 ` 2.5.60-mm2 Dave Jones
2003-02-14 9:58 ` 2.5.60-mm2 Andrew Morton
2003-02-14 10:13 ` 2.5.60-mm2 Dave Jones
2003-02-14 10:22 ` 2.5.60-mm2 Andrew Morton
2003-02-14 10:10 ` 2.5.60-mm2 Thomas Schlichter
2003-02-17 1:59 ` 2.5.60-mm2 Bill Davidsen
2003-02-17 12:08 ` 2.5.60-mm2 Bill Davidsen
2003-02-17 12:35 ` 2.5.60-mm2 Thomas Schlichter
2003-02-17 18:32 ` 2.5.60-mm2 Bill Davidsen
2003-02-15 20:27 ` 2.5.60-mm2 Arador
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox