From: Nick Piggin <nickpiggin@yahoo.com.au>
To: Badari Pulavarty <pbadari@us.ibm.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: 2.6.12-rc6-mm1 & 2K lun testing
Date: Thu, 16 Jun 2005 05:02:28 +1000 [thread overview]
Message-ID: <42B07B44.9040408@yahoo.com.au> (raw)
In-Reply-To: <1118860223.4301.449.camel@dyn9047017072.beaverton.ibm.com>
Badari Pulavarty wrote:
> On Wed, 2005-06-15 at 11:30, Nick Piggin wrote:
>
>>Badari Pulavarty wrote:
>>
>>
>>>------------------------------------------------------------------------
>>>
>>>elm3b29 login: dd: page allocation failure. order:0, mode:0x20
>>>
>>>Call Trace: <IRQ> <ffffffff801632ae>{__alloc_pages+990} <ffffffff801668da>{cache_grow+314}
>>> <ffffffff80166d7f>{cache_alloc_refill+543} <ffffffff80166e86>{kmem_cache_alloc+54}
>>> <ffffffff8033d021>{scsi_get_command+81} <ffffffff8034181d>{scsi_prep_fn+301}
>>
>>They look like they're all in scsi_get_command.
>>I would consider masking off __GFP_HIGH in the gfp_mask of that
>>function, and setting __GFP_NOWARN. It looks like it has a mempoolish
>>thingy in there, so perhaps it shouldn't delve so far into reserves.
>
>
> You want me to take off GFP_HIGH ? or just set GFP_NOWARN with GFP_HIGH
> ?
>
Yeah, take off GFP_HIGH and set GFP_NOWARN (always). I would be
interested to see how that goes.
Obviously it won't eliminate your failures there (it will probably
produce more of them), however it might help the scsi command
allocation from overwhelming the system.
THanks,
Nick
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-06-15 19:02 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 17:36 2.6.12-rc6-mm1 & 2K lun testing Badari Pulavarty
2005-06-15 18:30 ` Nick Piggin
2005-06-15 18:30 ` Badari Pulavarty
2005-06-15 19:02 ` Nick Piggin [this message]
2005-06-15 20:56 ` Badari Pulavarty
2005-06-16 1:48 ` Nick Piggin
2005-06-15 23:23 ` Dave Chinner
2005-06-15 21:39 ` Chen, Kenneth W
2005-06-15 22:35 ` Badari Pulavarty
2005-06-16 7:24 ` Andrew Morton
2005-06-16 19:50 ` Badari Pulavarty
2005-06-16 20:37 ` Andrew Morton
2005-06-16 23:43 ` Badari Pulavarty
2005-06-17 0:51 ` Andrew Morton
2005-06-17 15:10 ` Badari Pulavarty
2005-06-17 21:13 ` Andrew Morton
2005-06-22 0:34 ` 2.6.12-mm1 & 2K lun testing (JFS problem ?) Badari Pulavarty
2005-06-22 1:41 ` William Lee Irwin III
2005-06-22 16:23 ` Badari Pulavarty
2005-06-22 13:50 ` Dave Kleikamp
2005-06-22 16:56 ` Badari Pulavarty
2005-06-22 21:02 ` Badari Pulavarty
2005-06-16 22:42 ` 2.6.12-rc6-mm1 & 2K lun testing William Lee Irwin III
2005-06-16 22:25 ` Badari Pulavarty
2005-06-16 22:58 ` William Lee Irwin III
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=42B07B44.9040408@yahoo.com.au \
--to=nickpiggin@yahoo.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pbadari@us.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox