[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4807377b1003010937x8cea2c8hf1518eafb230cd88@mail.gmail.com>
Date: Mon, 1 Mar 2010 09:37:24 -0800
From: Jesse Brandeburg <jesse.brandeburg@...il.com>
To: Richard Hartmann <richih.mailinglist@...il.com>
Cc: e1000-devel@...ts.sf.net, linux-kernel@...r.kernel.org,
Andrew Pochinsky <avp@....edu>
Subject: Re: New thread: page allocation failure with E1000 (seems to be
reproducible)
in the future please copy netdev@...r.kernel.org on networking issues.
On Mon, Mar 1, 2010 at 9:34 AM, Richard Hartmann
<richih.mailinglist@...il.com> wrote:
> Hi Jesse,
>
>> the memory allocation (order:0), while unexpected, are not fatal, and
>> the e1000 driver is written to handle the failures during allocation.
>>
>> Does something else happen to the system after this or does operation continue?
>
> I can not be sure, but I _think_ some bogus data made it into userspace.
> I did have some binary in a text string I received & logged, which is a
> tad unusual.
hm, if that did occur it would be bad. But it does sound like
operation continued, which is good.
>> You might be able to try the sysctl tweak to reserve a little more
>> memory for driver allocations.
>> # sysctl vm.min_free_kbytes
>> # sysctl -e vm.min_free_kbytes=<double what you have>
>
> I will try that, thanks.
>
>
>> have you increased the number of rx/tx descriptors in use by e1000?
>
> No. Should I?
I wouldn't recommend it if you're already having issues getting
order:0 allocations, it would just make the problem worse. I wanted
to make sure you were not.
Jesse
--
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