All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Srivats P <pstavirs@gmail.com>
Cc: Xdp <xdp-newbies@vger.kernel.org>
Subject: Re: mlx5 AF_XDP zero-copy queues
Date: Sat, 13 Jul 2024 09:04:38 -0700	[thread overview]
Message-ID: <20240713090438.37e19696@kernel.org> (raw)
In-Reply-To: <CANzUK58QbpEgQGY-O1ixwZp=6VM92_ZZZcr83o3nomi=S0VArw@mail.gmail.com>

On Sat, 13 Jul 2024 12:23:31 +0530 Srivats P wrote:
> I'm seeing a behaviour difference between kernel 5.4 and 5.15 wrt the
> AF_XDP queues used for zero copy. This is specific to the mlx5.
> 
> Assume you have 'n' queues configured on the interface.
> 
> In 5.4, you had to use n to 2*n -1 queue numbers for AF_XDP zc. Using
> 0 to n-1 queues would use copy mode.
> 
> In 5.15, you have to use 0 to n-1 for zero copy also. Socket creation
> fails if you use queue >=n.
> 
> Also, with 5.4 netdev stats would not be incremented for AF_XDP
> packets whereas with 5.15 they do get incremented?
> 
> Can someone confirm this behaviour change or point me to relevant
> mailing list discussions or some other information on the same? My
> google-fu is failing me.
> 
> When did this change go into the kernel? I can't find anything in the
> kernelnewbies.org changelog between 5.4 and 5.15.

Hm, can't find the relevant commit quickly either now. But it's
intentional. The new behavior is how all other drivers work.
Hopefully this change isn't a deal breaker for anyone because
long term the lack of uniformity among drivers is a PITA.

  reply	other threads:[~2024-07-13 16:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-13  6:53 mlx5 AF_XDP zero-copy queues Srivats P
2024-07-13 16:04 ` Jakub Kicinski [this message]
2024-07-15 10:54   ` Srivats P
2024-07-17 10:05     ` Srivats P
     [not found]       ` <LO4P265MB3758D7056BF45389781B8C4193AC2@LO4P265MB3758.GBRP265.PROD.OUTLOOK.COM>
2024-07-18 11:59         ` Srivats P

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=20240713090438.37e19696@kernel.org \
    --to=kuba@kernel.org \
    --cc=pstavirs@gmail.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.