All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jesper Dangaard Brouer <brouer@redhat.com>
To: Christian Deacon <gamemann@gflclan.com>
Cc: xdp-newbies@vger.kernel.org, brouer@redhat.com
Subject: Re: Measuring/Debugging XDP Performance
Date: Thu, 23 Jan 2020 21:38:08 +0100	[thread overview]
Message-ID: <20200123213808.7a1f200b@carbon> (raw)
In-Reply-To: <23ec64c0-e0d7-a60b-ecc4-6ca401dc4896@gflclan.com>

On Thu, 23 Jan 2020 11:22:31 -0600
Christian Deacon <gamemann@gflclan.com> wrote:

> Thank you for the information and I will try these commands tonight when 
> there is higher traffic load! The 'perf' command seems interesting.

Thanks for the perf output in the private email thread. From the output
I can clearly see the problem (some copy pasted below signature).  You
are using the driver igb which does not support XDP-native, and is thus
using generic-XDP.

This driver only have 192 bytes headroom, where 256 is needed.  Thus,
running XDP-generic will be slower than running the normal network
stack, as every packet will get reallocated and copied.

-- 
Best regards,
  Jesper Dangaard Brouer
  MSc.CS, Principal Kernel Engineer at Red Hat
  LinkedIn: http://www.linkedin.com/in/brouer

     2.88%  swapper          [kernel.kallsyms]         [k] igb_poll
            |          
             --2.82%--igb_poll
                       |          
                        --2.45%--net_rx_action
                                  __softirqentry_text_start
                                  irq_exit



    0.71%  006  swapper          [kernel.kallsyms]         [k] page_frag_free
            |
            ---page_frag_free
               |          
                --0.68%--skb_free_head
                          pskb_expand_head
                          do_xdp_generic
                          netif_receive_skb_internal
                          napi_gro_receive
                          igb_clean_rx_irq
                          igb_poll
                          net_rx_action

  reply	other threads:[~2020-01-23 20:38 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-22 18:02 Measuring/Debugging XDP Performance Christian Deacon
2020-01-22 22:11 ` Vincent Li
2020-01-23 12:30   ` Jesper Dangaard Brouer
2020-01-23 13:11 ` Jesper Dangaard Brouer
2020-01-23 17:22   ` Christian Deacon
2020-01-23 20:38     ` Jesper Dangaard Brouer [this message]
2020-01-23 21:38       ` Christian Deacon
2020-01-28 18:55         ` Christian Deacon
2020-01-29  1:19           ` Matheus Salgueiro Castanho
     [not found]         ` <b1d478e6-555c-97da-f967-4f10f879f589@gflclan.com>
2020-01-29 12:09           ` Jesper Dangaard Brouer
2020-01-29 14:26           ` Jesper Dangaard Brouer
2020-01-30 14:53             ` Christian Deacon

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=20200123213808.7a1f200b@carbon \
    --to=brouer@redhat.com \
    --cc=gamemann@gflclan.com \
    --cc=xdp-newbies@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.