netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michal Schmidt <mschmidt@redhat.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: netdev@vger.kernel.org, Jerry Chu <hkchu@google.com>,
	Eric Dumazet <edumazet@google.com>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: significant napi_gro_frags() slowdown
Date: Thu, 27 Mar 2014 18:05:48 +0100	[thread overview]
Message-ID: <53345A6C.5080008@redhat.com> (raw)
In-Reply-To: <1395938874.12610.306.camel@edumazet-glaptop2.roam.corp.google.com>

Dne 27.3.2014 17:47, Eric Dumazet napsal:
> On Thu, 2014-03-27 at 17:39 +0100, Michal Schmidt wrote:
>> I received a report about a performance regression on a simple workload
>> of receiving a single TCP stream using a be2net NIC. Previously the
>> reporter was able to reach more than 9 Gb/s, but now he sees less than 7
>> Gb/s.
>
> Yeah, we are aware of this, and we had some discussions, but not yet got
> a fix.
>
> Are you running a 64 or 32bit kernel BTW ?

Both my reporter and I are running 64bit kernels.

Thanks,
Michal

  reply	other threads:[~2014-03-27 17:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27 16:39 significant napi_gro_frags() slowdown Michal Schmidt
2014-03-27 16:47 ` Eric Dumazet
2014-03-27 17:05   ` Michal Schmidt [this message]
2014-03-27 17:21     ` Eric Dumazet
2014-03-30  4:28       ` [PATCH net-next] net-gro: restore frag0 optimization Eric Dumazet
2014-03-31 20:27         ` David Miller
2014-03-31 21:01           ` Eric Dumazet
2014-03-31 21:19             ` Eric Dumazet
2014-04-01 16:40         ` Michal Schmidt
2014-04-01 17:16           ` Eric Dumazet

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=53345A6C.5080008@redhat.com \
    --to=mschmidt@redhat.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=hkchu@google.com \
    --cc=netdev@vger.kernel.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).