From: David Miller <davem@davemloft.net>
To: romieu@fr.zoreil.com
Cc: booster@wolke7.net, hayeswang@realtek.com, jrnieder@gmail.com,
eric.dumazet@gmail.com, netdev@vger.kernel.org,
nic_swsd@realtek.com, linux-kernel@vger.kernel.org,
armin.kazmi@tu-dortmund.de
Subject: Re: [PATCH 1/2] r8169: Rx FIFO overflow fixes.
Date: Mon, 05 Dec 2011 18:45:38 -0500 (EST) [thread overview]
Message-ID: <20111205.184538.809640991246086089.davem@davemloft.net> (raw)
In-Reply-To: <20111205063045.GA3103@electric-eye.fr.zoreil.com>
From: Francois Romieu <romieu@fr.zoreil.com>
Date: Mon, 5 Dec 2011 07:30:45 +0100
> Realtek has specified that the post 8168c gigabit chips and the post
> 8105e fast ethernet chips recover automatically from a Rx FIFO overflow.
> The driver does not need to clear the RxFIFOOver bit of IntrStatus and
> it should rather avoid messing it.
>
> The implementation deserves some explanation:
> 1. events outside of the intr_event bit mask are now ignored. It enforces
> a no-processing policy for the events that either should not be there
> or should be ignored.
>
> 2. RxFIFOOver was already ignored in rtl_cfg_infos[RTL_CFG_1] for the
> whole 8168 line of chips with two exceptions:
> - RTL_GIGA_MAC_VER_22 since b5ba6d12bdac21bc0620a5089e0f24e362645efd
> ("use RxFIFO overflow workaround for 8168c chipset.").
> This one should now be correctly handled.
> - RTL_GIGA_MAC_VER_11 (8168b) which requires a different Rx FIFO
> overflow processing.
>
> Though it does not conform to Realtek suggestion above, the updated
> driver includes no change for RTL_GIGA_MAC_VER_12 and RTL_GIGA_MAC_VER_17.
> Both are 8168b. RTL_GIGA_MAC_VER_12 is common and a bit old so I'd rather
> wait for experimental evidence that the change suggested by Realtek really
> helps or does not hurt in unexpected ways.
>
> Removed case statements in rtl8169_interrupt are only 8168 relevant.
>
> 3. RxFIFOOver is masked for post 8105e 810x chips, namely the sole 8105e
> (RTL_GIGA_MAC_VER_30) itself.
>
> Signed-off-by: Francois Romieu <romieu@fr.zoreil.com>
> Cc: hayeswang <hayeswang@realtek.com>
Applied.
next prev parent reply other threads:[~2011-12-05 23:45 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4E7F4D45.7040902@wolke7.net>
[not found] ` <1316978632.4122.103.camel@deadeye>
[not found] ` <4E82C0B5.1050902@wolke7.net>
[not found] ` <1317254171.4068.12.camel@deadeye>
[not found] ` <20111124044137.GA18262@elie.hsd1.il.comcast.net>
[not found] ` <4ECFE7A7.5070300@wolke7.net>
2011-11-25 20:19 ` [bug?] r8169: hangs under heavy load Jonathan Nieder
2011-11-25 20:31 ` Jonathan Nieder
2011-11-25 20:32 ` Eric Dumazet
2011-11-25 20:54 ` Jonathan Nieder
2011-11-25 21:05 ` Eric Dumazet
2011-11-25 22:22 ` Francois Romieu
2011-11-25 23:05 ` Eric Dumazet
2011-11-26 0:44 ` Francois Romieu
2011-11-26 4:07 ` Eric Dumazet
2011-11-27 9:28 ` Jonathan Nieder
2011-11-27 21:02 ` booster
2011-11-27 23:11 ` Francois Romieu
2011-11-29 6:47 ` hayeswang
2011-11-29 10:54 ` Francois Romieu
2011-11-29 19:56 ` booster
2011-12-01 10:20 ` Francois Romieu
2011-12-01 20:42 ` booster
2011-12-01 22:26 ` Francois Romieu
2011-12-05 6:30 ` [PATCH 1/2] r8169: Rx FIFO overflow fixes Francois Romieu
2011-12-05 23:45 ` David Miller [this message]
2012-02-20 2:37 ` Jonathan Nieder
2012-02-20 23:22 ` Francois Romieu
2011-12-05 6:30 ` [PATCH 2/2] r8169: fix Rx index race between FIFO overflow recovery and NAPI handler Francois Romieu
2011-12-05 23:45 ` David Miller
2011-12-02 2:21 ` [bug?] r8169: hangs under heavy load hayeswang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111205.184538.809640991246086089.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=armin.kazmi@tu-dortmund.de \
--cc=booster@wolke7.net \
--cc=eric.dumazet@gmail.com \
--cc=hayeswang@realtek.com \
--cc=jrnieder@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nic_swsd@realtek.com \
--cc=romieu@fr.zoreil.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).