From: Nix <nix@esperi.org.uk>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
rl@hellgate.ch, "Bjarke Istrup Pedersen" <gurligebis@gentoo.org>
Subject: Re: [PATCH RFT net-next #2 0/6] via-rhine receive buffers rework
Date: Wed, 08 Apr 2015 18:02:41 +0100 [thread overview]
Message-ID: <87vbh6364u.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <cover.1428445141.git.romieu@fr.zoreil.com> (Francois Romieu's message of "Wed, 8 Apr 2015 00:40:47 +0200")
On 7 Apr 2015, Francois Romieu stated:
> The series applies without error against v3.19 and davem-next as of
> 812034f11628aaaab0e2d7af1d3bc50a49eb396b ("cxgb4: Move ethtool related
> code to a separate file").
I am sorry to report that I just had a watchdog-triggered autoreboot
during testing of this patch series :( with no log messages of any kind.
looks like the underlying bug is still there, or another bug with the
same symptoms (i.e. some way to crash inside the rx handler). I qwish I
could get some debugging output when this happens!
However, to give some good news, CPU usage is much lower than before the
patch: si ~10%, rather than ~80% with spikes of full CPU usage:
ksoftirqd's CPU usage is steady at about 3% rather than 40--60% with
spikes to 100%, and some of that will be USB interrupts from the
continuous USB traffic from my entropy key.
--
NULL && (void)
next prev parent reply other threads:[~2015-04-08 17:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-07 22:40 [PATCH RFT net-next #2 0/6] via-rhine receive buffers rework Francois Romieu
2015-04-07 22:40 ` [PATCH net-next #2 1/6] via-rhine: commit receive buffer address before descriptor status update Francois Romieu
2015-04-07 22:40 ` [PATCH net-next #2 2/6] via-rhine: add allocation helpers Francois Romieu
2015-04-07 22:40 ` [PATCH net-next #2 3/6] via-rhine: gotoize rhine_open error path Francois Romieu
2015-04-07 22:40 ` [PATCH net-next #2 4/6] via-rhine: forbid holes in the receive descriptor ring Francois Romieu
2015-04-07 22:40 ` [PATCH net-next #2 5/6] via-rhine: kiss rx_head_desc goodbye Francois Romieu
2015-04-07 22:40 ` [PATCH net-next #2 6/6] via-rhine: beautify vlan receive code Francois Romieu
2015-04-08 17:02 ` Nix [this message]
2015-04-08 21:50 ` [PATCH RFT net-next #2 0/6] via-rhine receive buffers rework Francois Romieu
2015-04-08 22:43 ` Nix
2015-04-09 18:08 ` Nix
2015-04-09 22:41 ` Francois Romieu
2015-04-13 13:16 ` Nix
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=87vbh6364u.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=davem@davemloft.net \
--cc=gurligebis@gentoo.org \
--cc=netdev@vger.kernel.org \
--cc=rl@hellgate.ch \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.