[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20090901.184121.06750444.davem@davemloft.net>
Date: Tue, 01 Sep 2009 18:41:21 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: eric.dumazet@...il.com
Cc: cl@...ux-foundation.org, sri@...ibm.com, dlstevens@...ibm.com,
netdev@...r.kernel.org, niv@...ux.vnet.ibm.com,
mtk.manpages@...il.com
Subject: Re: [PATCH net-next-2.6] ip: Report qdisc packet drops
From: Eric Dumazet <eric.dumazet@...il.com>
Date: Mon, 31 Aug 2009 14:09:50 +0200
> Re-reading again this stuff, I realized ip6_push_pending_frames()
> was not updating IPSTATS_MIB_OUTDISCARDS, even if IP_RECVERR was set.
>
> May I suggest following path :
>
> 1) Correct ip6_push_pending_frames() to properly
> account for dropped-by-qdisc frames when IP_RECVERR is set
Your patch is applied to net-next-2.6, thanks!
> 2) Submit a patch to account for qdisc-dropped frames in SNMP counters
> but still return a OK to user application, to not break them ?
Sounds good.
I think if you sample random UDP applications, you will find that such
errors will upset them terribly, make them log tons of crap to
/var/log/messages et al., and consume tons of CPU.
And in such cases silent ignoring of drops is entirely appropriate and
optimal, which supports our current behavior.
If we are to make such applications "more sophisticated" such
converted apps can be indicated simply their use of IP_RECVERR.
If you want to be notified of all asynchronous errors we can detect,
you use this, end of story. It is the only way to handle this
situation without breaking the world.
As usual, Alexey Kuznetsov's analysis of this situation is timeless,
accurate, and wise. And he understood all of this 10+ years ago.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists