From: "Zdenek Kabelac" <zdenek.kabelac@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "Rik van Riel" <riel@redhat.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
yi.zhu@intel.com, reinette.chatre@intel.com,
linux-wireless@vger.kernel.org
Subject: Re: Problem: Out of memory after 2days with 2GB RAM
Date: Thu, 12 Jun 2008 16:12:18 +0200 [thread overview]
Message-ID: <c4e36d110806120712h1237d084v2eaeb494cc48b43c@mail.gmail.com> (raw)
In-Reply-To: <1213278884.3936.15.camel@johannes.berg>
2008/6/12 Johannes Berg <johannes@sipsolutions.net>:
> On Thu, 2008-06-12 at 09:38 -0400, Rik van Riel wrote:
>> On Thu, 12 Jun 2008 12:07:34 +0200
>> "Zdenek Kabelac" <zdenek.kabelac@gmail.com> wrote:
>>
>> > It looks like while there was a huge amount of buffers and caches -
>> > system was unable to allocate few pages for kmalloc in iwl3945 driver
>> > after resume.
>>
>> It looks like this is because it wants to allocate 2**5 contiguous
>> pages, which is 128kB of contiguous kernel memory.
>
> 64-bit system I assume?
> The allocation should be 256 * 20 * sizeof(struct sk_buff *).
>
> Try the patch below. It should improve code generation too.
I'll surely try you patch - but is the iwl the only driver which needs
128kB continuous memory chunk?
I think that if the 128kB memchunks are exhausted in 2 days while
there is over 1GB of free RAM in buffers & caches I think some
defragmentation is needed then ?
btw: Does it really means that within those buffers kernel could not
find any adjacent 32 pages which could be made free ?
Zdenek
next prev parent reply other threads:[~2008-06-12 14:12 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-12 10:07 Zdenek Kabelac
2008-06-12 13:38 ` Rik van Riel
2008-06-12 13:54 ` Johannes Berg
2008-06-12 14:12 ` Zdenek Kabelac [this message]
2008-06-12 14:19 ` Johannes Berg
2008-06-12 16:38 ` Tomas Winkler
2008-06-12 15:43 ` Tomas Winkler
2008-06-12 16:35 ` Tomas Winkler
2008-06-12 17:05 ` Johannes Berg
2008-06-12 17:39 ` Tomas Winkler
2008-06-12 17:46 ` Johannes Berg
2008-06-12 18:03 ` Tomas Winkler
2008-06-12 18:15 ` Johannes Berg
2008-06-12 20:11 ` Zdenek Kabelac
2008-06-12 22:17 ` Tomas Winkler
2008-06-13 0:43 ` Andrew Morton
2008-06-12 18:41 ` John W. Linville
2008-06-12 17:03 ` Johannes Berg
2008-06-12 17:35 ` Tomas Winkler
2008-06-12 17:39 ` Johannes Berg
2008-06-12 17:50 ` Tomas Winkler
2008-06-12 17:10 ` Rik van Riel
2008-06-12 21:30 ` Jiri Slaby
2008-06-12 22:26 ` Tomas Winkler
2008-06-13 14:08 ` Rafael J. Wysocki
2008-06-13 14:15 ` Zdenek Kabelac
2008-06-30 11:30 ` Zdenek Kabelac
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=c4e36d110806120712h1237d084v2eaeb494cc48b43c@mail.gmail.com \
--to=zdenek.kabelac@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.com \
--cc=riel@redhat.com \
--cc=yi.zhu@intel.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
all inboxes | Powered by JetHome®