All of lore.kernel.org
 help / color / mirror / Atom feed
From: kernel-stuff@comcast.net (Parag Warudkar)
To: Roy Keene <rkeene@psislidell.com>, linux-kernel@vger.kernel.org
Subject: Re: Problem with 2.6 kernel and lots of I/O
Date: Tue, 31 May 2005 16:12:13 +0000	[thread overview]
Message-ID: <053120051612.19940.429C8CDD000A6E5800004DE4220073407600009A9B9CD3040A029D0A05@comcast.net> (raw)

 > Info: Linux cog1 2.6.9-5.0.5.ELsmp #1 SMP Fri Apr 8 14:29:47 EDT 2005 i686 i686 
> i386 GNU/Linux
> Dist: RedHat Enterprise Linux 4
> Spec:
>      2 x 3.2GHz Xeon (each system, with hyperthreading so 4 logical processors)
>      4GB of physical RAM
>      2GB of configured swap (partition, contigious)
>      2 x 1000Mbps (Intel 82546GB) network cards (HA cluster link is
>                provided by a cross over cable between the two nodes)
> -

Since you are using a vendor kernel which is older than the current 2.6 kernel.org one - you are better off posting to appropriate vendor mailing  list or ask them for support if you have a contract. Or else, try to reproduce the problem with latest kernel.org kernel and then re-post the information here.

Parag



             reply	other threads:[~2005-05-31 16:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-31 16:12 Parag Warudkar [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-05-31 15:55 Problem with 2.6 kernel and lots of I/O Roy Keene
     [not found] ` <200505312040.30812.bernd-schubert@web.de>
2005-05-31 19:00   ` Roy Keene
2005-06-01  1:16     ` Kyle Moffett
2005-06-01 19:59 ` Pavel Machek
2005-06-05 10:11   ` Erik Slagter
2005-06-06  5:46     ` Kyle Moffett
2005-06-20 22:19       ` Roy Keene
2005-06-20 23:18         ` Kyle Moffett
2005-06-20 23:54           ` Roy Keene
2005-06-21  2:47             ` Kyle Moffett
2005-06-21  7:41             ` Pavel Machek
2005-06-21 14:23               ` Roy Keene

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=053120051612.19940.429C8CDD000A6E5800004DE4220073407600009A9B9CD3040A029D0A05@comcast.net \
    --to=kernel-stuff@comcast.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkeene@psislidell.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.