All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Coleman <pcoleman@iinet.net.au>
To: reiserfs-list@namesys.com
Subject: CPU usage problem with custom 2.6.7 kernel
Date: Sat, 14 Aug 2004 18:24:07 +0800	[thread overview]
Message-ID: <411DE847.3070809@iinet.net.au> (raw)

Hi,
I am using reiser3 on linux-2.6.7 on both a desktop and a fileserver. Intensive reading and writing
seem to be using 100% cpu on both, limiting the rate at which I can transfer stuff to/from the
fileserver to about 1Mb/s (on a 100MB/s network/800mhz Celeron server). The default slackware-2.4
kernel does not seem to have this problem (the slackware 2.6.7 kernel does not have reiserfs support
by default). Anyone have any ideas?

Thanks in advance,
Patrick

hdparm output (desktop) - 80gb (seagate), hda3 is 65gb reiser3:
pcoleman@hal:~$ sudo hdparm /dev/hda

/dev/hda:
   multcount    =  0 (off)
   IO_support   =  1 (32-bit)
   unmaskirq    =  1 (on)
   using_dma    =  1 (on)
   keepsettings =  0 (off)
   readonly     =  0 (off)
   readahead    = 256 (on)
   geometry     = 65535/16/63, sectors = 156301488, start = 0
pcoleman@hal:~$

hdparm output (server) - 120gb (western digital), one partition, hdb1 is 120gb reiser3:
admin@server:~$ sudo hdparm /dev/hda

/dev/hda:
   multcount    = 16 (on)
   IO_support   =  0 (default 16-bit)
   unmaskirq    =  0 (off)
   using_dma    =  0 (off)
   keepsettings =  0 (off)
   readonly     =  0 (off)
   readahead    = 256 (on)
   geometry     = 16383/255/63, sectors = 234441648, start = 0
admin@server:~$

I can supply kernel config files if required (the mailing list rejects messages over 40kb)


             reply	other threads:[~2004-08-14 10:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-14 10:24 Patrick Coleman [this message]
2004-08-14 10:36 ` CPU usage problem with custom 2.6.7 kernel Spam
2004-08-16 13:48   ` Chris Mason

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=411DE847.3070809@iinet.net.au \
    --to=pcoleman@iinet.net.au \
    --cc=reiserfs-list@namesys.com \
    /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.