From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: James Washer <washer@trlp.com>
Cc: linux-mm@kvack.org, ak@muc.de
Subject: Re: Question about OOM-Killer
Date: Sat, 23 Jul 2005 10:00:48 -0300 [thread overview]
Message-ID: <20050723130048.GA16460@dmt.cnet> (raw)
In-Reply-To: <20050718123650.01a49f31.washer@trlp.com>
James,
Can you send the OOM killer output?
I dont know which devices part of an x86-64 system should
be limited to 16Mb of physical addressing. Andi?
I don't think that any devices should have 16MB limitation
On Mon, Jul 18, 2005 at 12:36:50PM -0700, James Washer wrote:
> Sorry, I should have added...
> 2.6.11.10,
> x86-64 dual proc (Intel Xeon 3.4GHz)
> 6GiB ram
> Intel Corporation 82801EB (ICH5) SATA Controller (rev 0)
> Host: scsi0 Channel: 00 Id: 00 Lun: 00
> Vendor: ATA Model: Maxtor 6Y160M0 Rev: YAR5
> Type: Direct-Access ANSI SCSI revision: 05
> Host: scsi0 Channel: 00 Id: 01 Lun: 00
> Vendor: ATA Model: Maxtor 7Y250M0 Rev: YAR5
> Type: Direct-Access ANSI SCSI revision: 05
>
>
> On Mon, 18 Jul 2005 12:21:01 -0700
> James Washer <washer@trlp.com> wrote:
>
> > I'm chasing down a system problem where the DMA memory (x86-64, god knows why it is using DMA memory)
> drops below the minimum, and the OOM-Killer is fired off.
> >
> > It just strikes me odd that the OOM-Killer would be called at all for DMA memory.
> What's the chance of regaining DMA memory by killing user land processes?
> >
> > I'll admit, I know very little about linux VM, so perhaps I'm missing how oom killing can be helpful here.
--
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:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2005-07-23 13:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 19:21 Question about OOM-Killer James Washer
2005-07-18 19:36 ` James Washer
2005-07-23 13:00 ` Marcelo Tosatti [this message]
2005-07-25 19:11 ` James Washer
2005-07-25 12:27 ` Marcelo Tosatti
2005-07-25 22:41 ` Martin J. Bligh
2005-07-25 15:46 ` Marcelo Tosatti
2005-07-26 0:35 ` James Washer
2005-07-25 17:10 ` Marcelo Tosatti
2005-07-26 13:29 ` Martin J. Bligh
2005-07-26 15:17 ` Andi Kleen
2005-07-26 16:34 ` Martin J. Bligh
2005-07-26 16:34 ` Martin J. Bligh
2005-07-26 13:53 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2023-05-31 8:42 Question about oom-killer Gou Hao
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=20050723130048.GA16460@dmt.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=ak@muc.de \
--cc=linux-mm@kvack.org \
--cc=washer@trlp.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.