Linux RAID subsystem development
 help / color / mirror / Atom feed
From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, dan.j.williams@intel.com
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.26-rc8 deadlock: RAID code?
Date: Sun, 06 Jul 2008 02:49:04 -0400	[thread overview]
Message-ID: <20080706064904.10507.qmail@science.horizon.com> (raw)
In-Reply-To: <e9c3a7c20807050854o330279f7x3d64b1ec263f8800@mail.gmail.com>

"Dan Williams" <dan.j.williams@intel.com> wrote:
> Are you running with CONFIG_NUMA=n?  If so, you may be seeing the
> effects of kswapd not running. See the patch at:
>
>      http://marc.info/?l=linux-mm&m=121510360428340&w=2

Indeed I am.  My apologies for not including the kernel config.
That's in -rc9, so I've rebased to that and we'll see what happens.

Thank you so much!

      reply	other threads:[~2008-07-06  6:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-04 12:55 2.6.26-rc8 deadlock: RAID code? George Spelvin
2008-07-05 15:54 ` Dan Williams
2008-07-06  6:49   ` George Spelvin [this message]

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=20080706064904.10507.qmail@science.horizon.com \
    --to=linux@horizon.com \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox