DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Ciara Loftus <ciara.loftus@intel.com>, <dev@dpdk.org>
Subject: Re: [PATCH 2/2] net/af_xdp: reserve fill queue before socket create
Date: Fri, 18 Feb 2022 18:49:03 +0000	[thread overview]
Message-ID: <f872b14d-afd2-f989-4b23-68a4ce4d4de7@intel.com> (raw)
In-Reply-To: <20220218112037.61204-2-ciara.loftus@intel.com>

On 2/18/2022 11:20 AM, Ciara Loftus wrote:
> Some zero copy AF_XDP drivers eg. ice require that there are addresses
> already in the fill queue before the socket is created. Otherwise you may
> see log messages such as:
> 
> XSK buffer pool does not provide enough addresses to fill 2047 buffers on
> Rx ring 0
> 

I confirm the above log is gone with the patch,
for the record I am seeing below instead now:
[  +0.346578] ice 0000:86:00.1: Registered XDP mem model MEM_TYPE_XSK_BUFF_POOL on Rx ring 0
[  +0.032472] device enp134s0f1 left promiscuous mode

> This commit ensures that the addresses are available before creating the
> socket, instead of after.
> 
> Signed-off-by: Ciara Loftus<ciara.loftus@intel.com>

Tested-by: Ferruh Yigit <ferruh.yigit@intel.com>

  reply	other threads:[~2022-02-18 18:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-18 11:20 [PATCH 1/2] net/af_xdp: ensure xsk is deleted on Rx queue setup error Ciara Loftus
2022-02-18 11:20 ` [PATCH 2/2] net/af_xdp: reserve fill queue before socket create Ciara Loftus
2022-02-18 18:49   ` Ferruh Yigit [this message]
2022-02-18 18:49 ` [PATCH 1/2] net/af_xdp: ensure xsk is deleted on Rx queue setup error Ferruh Yigit

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=f872b14d-afd2-f989-4b23-68a4ce4d4de7@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=ciara.loftus@intel.com \
    --cc=dev@dpdk.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).