[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1ba2fa240806121039o376b0a8sdfaacf3a1f4a9e57@mail.gmail.com>
Date: Thu, 12 Jun 2008 20:39:27 +0300
From: "Tomas Winkler" <tomasw@...il.com>
To: "Johannes Berg" <johannes@...solutions.net>
Cc: "Rik van Riel" <riel@...hat.com>,
"Zdenek Kabelac" <zdenek.kabelac@...il.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
yi.zhu@...el.com, reinette.chatre@...el.com,
linux-wireless@...r.kernel.org
Subject: Re: Problem: Out of memory after 2days with 2GB RAM
On Thu, Jun 12, 2008 at 8:05 PM, Johannes Berg
<johannes@...solutions.net> wrote:
>
>> > Probably. it would be safe to use vmalloc for allocating txb anyway.
>> > I'll give it a try.
>>
>> So vmalloc didn't break anything on the 32bit machine I'm just about
>> to install 64 one so it will take hour or two.. I will issue some
>> official patch after that.
>
> Well, I disagree, and I'll push my patch as soon as somebody confirms
> that it doesn't break anything.
Remember you are not a maintainer of this driver and second we are
open to all suggestions you don't have to use this kind of
statements...
>
>> > There was already discussion on LKML about memory allocation problems
>> > on X86_64, which might explain this regression. This didn't happen
>> > before.
>>
>> This is the thread title if you are interested.
>> 'x86/kernel/pci_dma.c: gfp |= __GFP_NORETRY'
>
> Like I said, it doesn't matter, there's no need to _waste_
> 18*256*sizeof(void *) bytes memory.
It does matter this is not pci allocation we are saving in your patch.
> johannes
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists