From: Matt Domsch <Matt_Domsch@dell.com>
To: Mark Haverkamp <markh@osdl.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: out of memory question
Date: Fri, 28 Jan 2005 13:14:58 -0600 [thread overview]
Message-ID: <20050128191458.GA21601@lists.us.dell.com> (raw)
In-Reply-To: <1106934186.27858.40.camel@markh1.pdx.osdl.net>
On Fri, Jan 28, 2005 at 09:43:06AM -0800, Mark Haverkamp wrote:
>
> I have a situation where the out of memory killer kicked in and killed
> off a process. From the information displayed, it looks like there was
> a lot of free memory available. I need some help interpreting the
> output. I have included the console output from the oom killer.
>
> It is running 2.6.11-rc2 and has a patch from Nick Piggin:
> http://marc.theaimsgroup.com/?l=linux-kernel&m=110665524811826&w=2
> The machine is running as an iscsi target with 4K luns configured.
What is eating all of your ZONE_DMA? Of the 16MB available
> DMA: 55*4kB 4*8kB 2*16kB 0*32kB 1*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 348kB
> DMA free:348kB min:68kB low:84kB high:100kB active:4kB inactive:0kB present:16384kB pages_scanned:0 all_unreclaimable? no
> protections[]: 0 0 0
only 348kB is available, and something is requesting more...
> oom-killer: gfp_mask=0xd1 (__GFP_FS|__GFP_IO|__GFP_WAIT|__GFP_DMA)
This isn't a 64-bit architecture (you've got some ZONE_HIGHMEM), so
it's not like the x86_64/ia64 iommu. Perhaps a
<32-bit DMA address mask PCI device?
Thanks,
Matt
--
Matt Domsch
Software Architect
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
next prev parent reply other threads:[~2005-01-28 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 17:43 out of memory question Mark Haverkamp
2005-01-28 19:14 ` Matt Domsch [this message]
2005-01-28 19:21 ` Mark Haverkamp
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=20050128191458.GA21601@lists.us.dell.com \
--to=matt_domsch@dell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markh@osdl.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