public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: linux-kernel@vger.kernel.org
To: Catalin BOIE <util@deuroconsult.ro>
Cc: "Robert M. Hyatt" <hyatt@cis.uab.edu>,
	Nick Piggin <piggin@cyberone.com.au>,
	linux-kernel@vger.kernel.org, linux-smp@vger.kernel.org
Subject: Re: 2.6.2-rc2 Interactivity problems with SMP + HT
Date: Sun, 01 Feb 2004 16:00:31 -0500	[thread overview]
Message-ID: <401D68EF.9030109@tmr.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0401300919520.8217@hosting.rdsbv.ro>

Catalin BOIE wrote:
> On Thu, 29 Jan 2004, Robert M. Hyatt wrote:
> 
> 
>>
>>It might be some IDE disk I/O that results from flushing buffers or
>>whatever.  I don't see this on my SCSI boxes, but I have seen an IDE
>>box get sluggish at times due to I/O.
> 
> 
> It is possible.
> vmstat shows a lot of writes when this happen.
> Seems that even reads hangs.
> I remember tat I was in pine and I tried to save a small file (under 1k)
> and it took 5-7 seconds to do it.
> 
> 
>>On Thu, 29 Jan 2004, Nick Piggin
>>wrote:
>>
>>
>>>
>>>Catalin BOIE wrote:
>>>
>>>
>>>>Hello!
>>>>
>>>>First, thank you very much for the effort you put for Linux!
>>>>
>>>>I have a Intel motherboard with SATA (2 Maxtor disks).
>>>>CPUs: 2 x 2.4GHz PIV HT = 4 processors (2 virtual)
>>>>1 GB RAM.
>>>>
>>>>Load: postgresql and apache. Very low load (3-4 clients).
>>>>
>>>>RAID: Yes, soft RAID1 between the 2 disks.
>>>>
>>>>I have times when the console freeze for 3-4 seconds!
>>>>2.6.0-test11 had the same problem (maybe longer times).
>>>>2.6.1-rc2 worked good in this respect but crashed after 2 days. :(
>>>>2.6.2-rc2 is back with the delay.
>>>>
>>>>Do you know why this can happen?
>>>>
>>>>
>>>
>>>There haven't been many scheduler changes there recently so
>>>maybe its something else.
>>>
>>>But you could try the latest -mm kernels. They have some
>>>Hyperthreading work in them (you need to enable CONFIG_SCHED_SMT).

Another possible improvement might come from the recent ide changes 
posted here for evaluation. There was a change to not block all devices 
or even all devices on a cable if one device delayed. I believe it was 
if a command didn't finish as intended, but I don't have it handy since 
I sent it off for testing tomorrow on a system which may have that problem.

There's a good bit of work on hangs happening right now, so you could 
wait or dig up the patches and try them. I think they were by Davin 
McCall if memory serves.


-- 
bill davidsen <davidsen@tmr.com>
   CTO TMR Associates, Inc
   Doing interesting things with small computers since 1979

  parent reply	other threads:[~2004-02-01 20:58 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-29 10:44 2.6.2-rc2 Interactivity problems with SMP + HT Catalin BOIE
2004-01-29 10:49 ` Nick Piggin
2004-01-29 11:35   ` Catalin BOIE
2004-01-29 15:02   ` Robert M. Hyatt
2004-01-30  7:25     ` Catalin BOIE
2004-01-30 15:33       ` Gene Heskett
2004-01-30 20:09         ` Andrew Morton
2004-02-01 21:00       ` Bill Davidsen [this message]
2004-02-02 13:03         ` Catalin BOIE

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=401D68EF.9030109@tmr.com \
    --to=davidsen@tmr.com \
    --cc=hyatt@cis.uab.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-smp@vger.kernel.org \
    --cc=piggin@cyberone.com.au \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox