From: Stephen Hemminger <stephen@networkplumber.org>
To: Sylvain Vasseur <remmog@gmail.com>
Cc: users@dpdk.org
Subject: Re: ETH_RSS_NONFRAG_IPV4_UDP with netvsc, and memory setup for mlx4
Date: Thu, 12 May 2022 11:31:30 -0700 [thread overview]
Message-ID: <20220512113130.2c0e46be@hermes.local> (raw)
In-Reply-To: <CABVe3HOvi0nv6ajUJFBkArLNpndgd0bphNiqserVUvS8Xe3-Yg@mail.gmail.com>
On Thu, 12 May 2022 19:09:19 +0100
Sylvain Vasseur <remmog@gmail.com> wrote:
> Hello,
>
> I have been trying to use the netvsc PMD driver lately and face an issue
> with the RSS flag for UDP.
> I figured that this is because the PMD does not handle NDIS_HASH_UDP_IPV4,
> so I am planning at trying to submit a change to the PMD, however I am
> unsure about the value of the UDP constant. I found on
> https://microsoft.github.io/windows-docs-rs/doc/windows/Win32/NetworkManagement/Ndis/constant.NDIS_HASH_UDP_IPV4.html
> that it should be 0x00004000.
> Would someone have some proper knowledge about this specific setting?
>
> And after having used that change locally, I am now facing some issues with
> the mlx4 PMD used under the hood of netvsc. My memory allocation makes my
> buffers exist at a different location than my memory pool and this creates
> an issue:
> net_mlx4: port 0 unable to find virtually contiguous chunk for address
> Did someone already tried to use some custom memory management with the mlx
> pmd?
>
> Thanks,
> Sylvain
It should be able to do UDP hash (for non-fragmented packets only).
Look at FreeBSD:
https://github.com/freebsd/freebsd-src/tree/main/sys/dev/hyperv/netvsc
And Linux kernel:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/hyperv/rndis_filter.c
The Linux driver is the definitive source.
The FreeBSD driver is where netvsc PMD was derived from.
prev parent reply other threads:[~2022-05-12 18:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 18:09 Sylvain Vasseur
2022-05-12 18:31 ` Stephen Hemminger [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220512113130.2c0e46be@hermes.local \
--to=stephen@networkplumber.org \
--cc=remmog@gmail.com \
--cc=users@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).