All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nieścierowicz Adam" <adam.niescierowicz@justnet.pl>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Netdev <netdev@vger.kernel.org>
Subject: Re: 3.4.1 and 3.5-rc1 Packet lost at 250Mb/s
Date: Mon, 08 Oct 2012 12:49:53 +0200	[thread overview]
Message-ID: <80bb011e8f1289218087633fd7b115ea@justnet.pl> (raw)
In-Reply-To: <1349689640.21172.3008.camel@edumazet-glaptop>

W dniu 08.10.2012 11:47, Eric Dumazet napisał(a):

> On Mon, 2012-10-08 at 11:29 +0200, Nieścierowicz Adam wrote:
>
>>> You should use RPS on eth2/eth3 because they are non multi queue.
>>> Documentation/networking/scaling.txt should give you all the needed
>>> info
>> I set processors for rps such as affinity, unfortunately it did not
>> help --- cat /sys/class/net/eth{2,3,4,5}/queues/rx-0/rps_cpus 0040 
>> 0080
>> 0100 0200 --- CPU affinity http://wklej.org/id/843161/ [1]
>
> I said eth2 and eth3
>

eth2,eth3 and eth4,eth5 is the same card so I changed them as well, or 
made ​​a mistake?

> And you should use cpu11->cpu15 instead of cpu6->cpu9 since they are 
> in
> use...
>

I read in the file Documentation/networking/scaling.txt
---
if the rps_cpus for each queue are the ones that
share the same memory domain as the interrupting CPU for that queue
---

so i used the same CPU, I misunderstood?


> Anyway you dont say where are drops, (ifconfig give us very few 
> drops)

you can see no losses(drop), but a temporary decline in traffic on the 
interface to 0kb/s

>
> Also your eth0 seems to have a strange balance :
>
> RX interrupts seems to be well balanced on 4 queues :
>
> 76: 503 0 169271690 0 0 0 PCI-MSI-edge eth0-rx-0
> 77: 405 0 0 164532538 0 0 PCI-MSI-edge eth0-rx-1
> 78: 408 0 0 0 152778723 0 PCI-MSI-edge eth0-rx-2
> 79: 349 0 0 0 0 155011301 PCI-MSI-edge eth0-rx-3
> 80: 144 0 443432394 0 0 0 PCI-MSI-edge eth0-tx-0
> 81: 18 0 0 2043311 0 0 PCI-MSI-edge eth0-tx-1
> 82: 30 0 0 0 1934537 0 PCI-MSI-edge eth0-tx-2
> 83: 137 0 0 0 0 1968272 PCI-MSI-edge eth0-tx-3
>
> But TX seems to mostly use queue 0
>
> Packets sent to eth0 are coming from where ?

Packets come mainly from two routers(Edge BGP and local NAT)

  reply	other threads:[~2012-10-08 10:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-07 19:18 3.4.1 and 3.5-rc1 Packet lost at 250Mb/s Nieścierowicz Adam
2012-10-08  6:22 ` Eric Dumazet
2012-10-08  9:29   ` Nieścierowicz Adam
2012-10-08  9:47     ` Eric Dumazet
2012-10-08 10:49       ` Nieścierowicz Adam [this message]
2012-10-08 12:00         ` Andre Tomt
2012-10-08 12:06           ` Nieścierowicz Adam
2012-10-08 12:13           ` Eric Dumazet
2012-10-08 12:32             ` Andre Tomt
2012-10-08 12:59               ` Andre Tomt
2012-10-09 19:56                 ` Nieścierowicz Adam
2012-10-10  4:59                   ` Jeff Kirsher
  -- strict thread matches above, loose matches on Subject: below --
2012-07-06  9:47 Nieścierowicz Adam
2012-07-06 10:13 ` Eric Dumazet
2012-06-08  9:31 Nieścierowicz Adam
2012-06-08  8:58 Nieścierowicz Adam
2012-06-08  9:41 ` Eric Dumazet
2012-06-08  9:43   ` 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=80bb011e8f1289218087633fd7b115ea@justnet.pl \
    --to=adam.niescierowicz@justnet.pl \
    --cc=eric.dumazet@gmail.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 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.