From: hayeswang <hayeswang@realtek.com>
To: "'Francois Romieu'" <romieu@fr.zoreil.com>
Cc: <booster@wolke7.net>, "'Jonathan Nieder'" <jrnieder@gmail.com>,
"'Eric Dumazet'" <eric.dumazet@gmail.com>,
<netdev@vger.kernel.org>, "'nic_swsd'" <nic_swsd@realtek.com>,
<linux-kernel@vger.kernel.org>,
"'Armin Kazmi'" <armin.kazmi@tu-dortmund.de>
Subject: RE: [bug?] r8169: hangs under heavy load
Date: Fri, 2 Dec 2011 10:21:08 +0800 [thread overview]
Message-ID: <FCF60BC8872E4F1C9C72CE56F0E570C0@realtek.com.tw> (raw)
In-Reply-To: <20111129105440.GA2410@electric-eye.fr.zoreil.com>
Francois Romieu [mailto:romieu@fr.zoreil.com]
[...]
> > For the 8168c and the later chips, our hardware engineer
> says that don't enable
> > the RxFIFOOver of IntrMask and don't clear the RxFIFOOver
> of IntrStatus. The
> > hardware will automatically escape Rx fifo full situation.
> Although you try to
> > clear the RxFIFOOver of IntrStatus, maybe the bit wouldn't
> be cleared. Just
> > disregard it.
>
> Should "later" be understood as gigabit PCI-E only or is
> there a similar
> difference of behavior between older fast-ethernet PCI-E and
> more recent
> ones ?
>
For the fast controller, it should start from rtl8105e.
Best Regards,
Hayes
prev parent reply other threads:[~2011-12-02 2:21 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 ` 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
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 ` hayeswang [this message]
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=FCF60BC8872E4F1C9C72CE56F0E570C0@realtek.com.tw \
--to=hayeswang@realtek.com \
--cc=armin.kazmi@tu-dortmund.de \
--cc=booster@wolke7.net \
--cc=eric.dumazet@gmail.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
all inboxes | Powered by JetHome®