From: Nix <nix@esperi.org.uk>
To: Francois Romieu <romieu@fr.zoreil.com>
Cc: rl@hellgate.ch, Bjarke Istrup Pedersen <gurligebis@gentoo.org>,
"David S. Miller" <davem@davemloft.net>,
Linux-Netdev <netdev@vger.kernel.org>
Subject: Re: 3.19+: (and quite probably earlier) VIA Rhine hanging under high network load, yet again: redux
Date: Sat, 04 Apr 2015 22:26:39 +0100 [thread overview]
Message-ID: <87k2xr60vk.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <20150404210518.GA7698@electric-eye.fr.zoreil.com> (Francois Romieu's message of "Sat, 4 Apr 2015 23:05:18 +0200")
On 4 Apr 2015, Francois Romieu told this:
> Nix <nix@esperi.org.uk> :
> [...]
>
> This driver leaves holes in its receive ring under memory pressure.
> It may not help.
... OK so that is something I really should have spotted. I wasn't
looking at the driver's response to memory-shortage conditions because
this machine, though swapless, has wads of memory free under normal
conditions:
nix@fold 2 /home/nix% cat /proc/meminfo
MemTotal: 515720 kB
MemFree: 376552 kB
MemAvailable: 417120 kB
But of course this is networking, so we need skb_allocable memory, which
might be in much shorter supply than merely reclaimable/available memory
(though, again, 376552kB should be enough, you'd think).
> You can try the gross patch below against v3.19. It compiles. I have to go.
All I can say is "good grief, a response at Eastertime?! Valour beyond
the call of duty!"
I'll give it a try tomorrow :) but whether it works or not, I owe you a
drink next time you're in the UK south-east for spending any time at all
on this at Easter!
--
NULL && (void)
next prev parent reply other threads:[~2015-04-04 21:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-04 18:03 3.19+: (and quite probably earlier) VIA Rhine hanging under high network load, yet again: redux Nix
2015-04-04 21:05 ` Francois Romieu
2015-04-04 21:26 ` Nix [this message]
2015-04-05 4:01 ` David Miller
2015-04-05 20:59 ` Nix
2015-04-05 23:15 ` Francois Romieu
2015-04-05 23:29 ` 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=87k2xr60vk.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.