[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGVrzcZwGcs1DTTzUXTz3ydX=mmpAoJvEDB_5R9juLUucrzMNQ@mail.gmail.com>
Date: Wed, 11 Mar 2015 11:17:44 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Petri Gynther <pgynther@...gle.com>
Cc: netdev <netdev@...r.kernel.org>,
David Miller <davem@...emloft.net>,
Jaedon Shin <jaedon.shin@...il.com>
Subject: Re: [PATCH net-next v2] net: bcmgenet: collect Rx discarded packet count
2015-03-11 10:59 GMT-07:00 Petri Gynther <pgynther@...gle.com>:
> I find the Rx discard counter very useful, as it indicates HW dropped
> packets, which directly affects media playback quality.
I do not question the usefulness of that counter, I am wondering about
whether we could make sure we deal with this counter in a slow/error
path, I guess the answer to my previous question is no, because having
interrupts off for too long does not mean the CPU ran out of memory
for incoming packets.
In that case, this patch is fine as-is.
>
> In our unit tests, we actually discovered a major interrupts-off
> offender with this. Even with a moderate Rx traffic, we were seeing Rx
> discards. It turned out that using a large dmesg log buffer and
> dumping it with "cat /proc/kmsg" held interrupts off for long enough
> that bcmgenet experienced discards. It was very useful to have the
> discard data available when debugging this.
That is completely fair, it is just that I did a lot of performance
optimization before, and any expensive register in the hot-path is a
big no-no because that impacts your small packet performance (and thus
larger packet performance as well).
--
Florian
--
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