linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: w@1wt.eu (Willy Tarreau)
To: linux-arm-kernel@lists.infradead.org
Subject: Issue found in Armada 370: "No buffer space available" error during continuous ping
Date: Tue, 2 Dec 2014 07:56:31 +0100	[thread overview]
Message-ID: <20141202065631.GA22506@1wt.eu> (raw)
In-Reply-To: <CAB8gEUuE8GK=Pab1agvJS5y=+fKLwhJ4LYXFpxOd-Frtke5d1w@mail.gmail.com>

Hi Maggie,

On Tue, Dec 02, 2014 at 12:09:05PM +0800, Maggie Mae Roxas wrote:
> Hi Willy, Thomas,
> Good day.
> 
> This is just to confirm that the patch Willy sent yesterday, patched
> to 3.13.9 alone, resolves these issues:
> - "No buffer space available" around 17th packet
> - Low throughput on iperf as client (ie, ~130 Mbits/s on 1000 Mbits/s)
> - Kernel crash
> 
> We confirmed it after quite some testing.
> # Full logs at:
> # as iperf client: https://app.box.com/s/5pzh753dmmnqt4q8s5iy
> # as iperf server: https://app.box.com/s/t9ohxrcphpmnfer9dtj9
> 
> Thank you very much for your assistance again!!! :)

thanks for your valuable feedback, I'll add your tested-by and will
send it to netdev for inclusion before I switch to something else
and forget again!

Willy

  reply	other threads:[~2014-12-02  6:56 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08  2:20 Issue found in Armada 370: "No buffer space available" error during continuous ping Maggie Mae Roxas
2014-07-08  2:27 ` Maggie Mae Roxas
2014-07-08  8:21   ` Thomas Petazzoni
2014-07-09  6:35     ` Maggie Mae Roxas
2014-07-14  3:55       ` Maggie Mae Roxas
2014-07-15 12:24       ` Thomas Petazzoni
2014-07-15 12:43         ` Willy Tarreau
2014-07-17  5:37           ` Maggie Mae Roxas
2014-07-17  8:15             ` Willy Tarreau
2014-07-21  1:57               ` Maggie Mae Roxas
2014-07-21  2:45                 ` Maggie Mae Roxas
2014-07-21  5:44                   ` Willy Tarreau
2014-07-21  6:33                     ` Maggie Mae Roxas
2014-07-21  7:03                       ` Willy Tarreau
2014-07-23  2:24                         ` Maggie Mae Roxas
2014-07-23  6:16                           ` Willy Tarreau
2014-07-24  7:24                             ` Maggie Mae Roxas
2014-12-01  6:35                               ` Maggie Mae Roxas
     [not found]                               ` <CAB8gEUtgo-8nets3tRtqiZ8qRx+SyCq2d8v05scavWNwE5TNXg@mail.gmail.com>
2014-12-01  7:28                                 ` Willy Tarreau
2014-12-01  8:27                                   ` Maggie Mae Roxas
2014-12-01  9:28                                     ` Willy Tarreau
2014-12-01  9:32                                       ` Thomas Petazzoni
2014-12-01  9:58                                         ` Willy Tarreau
2014-12-01 10:15                                           ` Maggie Mae Roxas
2014-12-02  4:09                                             ` Maggie Mae Roxas
2014-12-02  6:56                                               ` Willy Tarreau [this message]
2014-12-02  7:04                                                 ` Maggie Mae Roxas

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=20141202065631.GA22506@1wt.eu \
    --to=w@1wt.eu \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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).