All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Leblond <eric@regit.org>
To: Jesper Dangaard Brouer <brouer@redhat.com>
Cc: xdp-newbies@vger.kernel.org
Subject: Re: CPU redirect and skb mode
Date: Thu, 04 Jan 2018 08:59:53 +0100	[thread overview]
Message-ID: <1515052793.7473.14.camel@regit.org> (raw)
In-Reply-To: <20180104081500.73d55bd8@redhat.com>

Hello Jesper,

On Thu, 2018-01-04 at 08:15 +0100, Jesper Dangaard Brouer wrote:
> On Thu, 04 Jan 2018 01:18:29 +0100 Eric Leblond <eric@regit.org>
> wrote:
> 
> > Hello,
> > 
> > I'm currently working on implementing XDP CPU redirect map inside
> > Suricata.
> > 
> > I've used CPU redirect map on my test laptop that has only skb mode
> > available and my implementation was failing with result being
> > almost
> > all packets if not all were dropped.
> 
> Remember that the tool xdp_monitor helps identify if XDP drops
> packets.
> (It's on my TODO list to expose the return values, until now I've
> just
> used the existing perf record/script to inspect the individual return
> ERRNO's when I needed more details).
> 
> Maybe suricata should attach itself to the XDP error tracepoints, to
> help the user experience?

Gonna look at it and see if it is doable.
> 
> > So I decided to build the XPD sample and test them:
> > 
> > sudo ./xdp_redirect_cpu --debug -d wlan0  --cpu 4 -S
> 
> I notice the -S option, which long option is --skb-mode.

Yes, I don't have a network card with XDP enable driver available on my
laptop.

> > The result was the same with packet blocked.
> > 
> > Am I missing something in the setup ?
> 
> The cpumap redirect feature does not for for skb-mode. 
> 
> It's on my TODO-list to make it work for skb-mode, but I got
> side-tracked after netconf (implementing xdp_rxq_info).  From a
> performance PoV it goes against the basic idea of CPUMAP, which is to
> move the SKB allocation to another CPU.

I second that, this is just pointless.

>   But for completeness sake I
> will implement this, it just requires the cpumap-code handle both
> xdp_buff's and SKB's in its queue.

Or you could just error if ever a BOF with CPU redirect is used in a
skb-mode ?

++
-- 
Eric Leblond <eric@regit.org>
Blog: https://home.regit.org/

  reply	other threads:[~2018-01-04  7:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-04  0:18 CPU redirect and skb mode Eric Leblond
2018-01-04  7:15 ` Jesper Dangaard Brouer
2018-01-04  7:59   ` Eric Leblond [this message]
2018-01-04  9:58     ` Jesper Dangaard Brouer

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=1515052793.7473.14.camel@regit.org \
    --to=eric@regit.org \
    --cc=brouer@redhat.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.