[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51A521DA.2080206@redhat.com>
Date: Tue, 28 May 2013 17:30:02 -0400
From: Rik van Riel <riel@...hat.com>
To: Francois Romieu <romieu@...zoreil.com>
CC: atomlin@...hat.com, netdev@...r.kernel.org, davem@...emloft.net,
edumazet@...gle.com, pshelar@...ira.com, mst@...hat.com,
alexander.h.duyck@...el.com, aquini@...hat.com,
sergei.shtylyov@...entembedded.com, linux-kernel@...r.kernel.org
Subject: Re: [Patch v2] skbuff: Hide GFP_ATOMIC page allocation failures for
dropped packets
On 05/27/2013 06:41 PM, Francois Romieu wrote:
> atomlin@...hat.com <atomlin@...hat.com> :
> [...]
>> Failed GFP_ATOMIC allocations by the network stack result in dropped
>> packets, which will be received on a subsequent retransmit, and an
>> unnecessary, noisy warning with a kernel backtrace.
>>
>> These warnings are harmless, but they still cause users to panic and
>> file bug reports over dropped packets. It would be better to hide the
>> failed allocation warnings and backtraces, and let retransmits handle
>> dropped packets quietly.
>
> Linux VM may be perfect but device drivers do stupid things.
>
> Please don't paper over it just because some shit ends in your backyard.
It is impossible to free memory at the speed at which
10Gbit network packets can come in.
Dropped packets are a reality.
The network stack already has statistics counters to
keep track of dropped packets. There is absolutely
no reason to print out an entire kernel backtrace
for dropped network packets.
All that achieves is get people to file bug reports,
which nothing can be done about. Oh, and distract
them from whatever issue as causing their actual
problem, and delay them fixing what was going on.
--
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