Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Aaron Wood <woody77@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	cake@lists.bufferbloat.net, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Cake] [Bloat] are anyone playing with dpdk and vpp?
Date: Wed, 27 Apr 2016 15:40:19 -0700	[thread overview]
Message-ID: <CALQXh-NqAOTjex7mma1w72Dx9FeFKFB9-8XudaZ7VVpJ6xb5qw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7Z=LKiesks9X3wWS2xu-U+AW0nhquO4_MPDtRzfkgmUw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 894 bytes --]

> where the tx and rx rings are cleaned up in the same thread and there
> is only one interrupt line for both.
>
>   51:         18      59244     253350     314273   PCI-MSI
> 1572865-edge      enp3s0-TxRx-0
>   52:          5     484274     141746     197260   PCI-MSI
> 1572866-edge      enp3s0-TxRx-1
>   53:          9     152225      29943     436749   PCI-MSI
> 1572867-edge      enp3s0-TxRx-2
>   54:         22      54327     299670     360356   PCI-MSI
> 1572868-edge      enp3s0-TxRx-3
>   56:     525343     513165    2355680     525593   PCI-MSI
> 2097152-edge      ath10k_pci
>
> and the ath10k only uses one interrupt. Maybe I'm wrong on my
> assumptions, I'd think in today's multi-core environment that
> processing tx and rx separately might be a win. (?)
>

The TX interrupt is used to free the SKB after the DMA from memory to the
NIC, correct? (hard_start_xmit()?)

-Aaron

[-- Attachment #2: Type: text/html, Size: 1306 bytes --]

      parent reply	other threads:[~2016-04-27 22:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-27 18:57 [Cake] " Dave Taht
2016-04-27 19:28 ` [Cake] [Bloat] " Aaron Wood
2016-04-27 19:32   ` Stephen Hemminger
2016-04-27 19:37     ` Mikael Abrahamsson
2016-04-27 19:45     ` Dave Taht
2016-04-27 19:50       ` Dave Taht
2016-04-27 22:40       ` Aaron Wood [this message]

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

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALQXh-NqAOTjex7mma1w72Dx9FeFKFB9-8XudaZ7VVpJ6xb5qw@mail.gmail.com \
    --to=woody77@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=stephen@networkplumber.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