All of lore.kernel.org
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: "Gregory K. Ruiz-Ade" <gregory@castandcrew.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.20 instability on bigmem systems?
Date: Thu, 13 Mar 2003 17:53:46 -0800	[thread overview]
Message-ID: <20030314015346.GJ20188@holomorphy.com> (raw)
In-Reply-To: <200303131745.28683.gregory@castandcrew.com>

On Thursday 13 March 2003 16:42, William Lee Irwin III wrote:
>> Hmm, slabinfo would be very helpful, as well as meminfo.

On Thu, Mar 13, 2003 at 05:45:28PM -0800, Gregory K. Ruiz-Ade wrote:
> I'll have to schedule a reboot into that kernel, but I'll try to get it 
> tonight if at all possible.

That's fine; I'm not in a hurry. =)


On Thursday 13 March 2003 16:42, William Lee Irwin III wrote:
>> You might need bh stuff (memclass-related or something like it) if it's
>> general disk io. Can't be too sure until slabinfo + meminfo materialize.

On Thu, Mar 13, 2003 at 05:45:28PM -0800, Gregory K. Ruiz-Ade wrote:
> I'm not familiar with "bh"... where can I read up on what it is?

bh == buffer_head. fs/buffer_head.c has the code.


-- wli

  reply	other threads:[~2003-03-14  1:43 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-14  0:27 2.4.20 instability on bigmem systems? Gregory K. Ruiz-Ade
2003-03-14  0:42 ` William Lee Irwin III
2003-03-14  1:45   ` Gregory K. Ruiz-Ade
2003-03-14  1:53     ` William Lee Irwin III [this message]
2003-03-14  3:55       ` Gregory K. Ruiz-Ade
2003-03-14  4:13         ` William Lee Irwin III
2003-03-14 17:31           ` Gregory K. Ruiz-Ade
2003-03-14 20:08             ` William Lee Irwin III
2003-03-17  2:15               ` Gregory K. Ruiz-Ade
2003-03-17  2:26                 ` William Lee Irwin III
2003-03-17  4:59                   ` Gregory K. Ruiz-Ade
2003-03-17  5:38                     ` Gregory K. Ruiz-Ade
2003-03-14 18:31 ` Martin J. Bligh

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=20030314015346.GJ20188@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=gregory@castandcrew.com \
    --cc=linux-kernel@vger.kernel.org \
    /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.