DPDK patches and discussions
 help / color / mirror / Atom feed
From: longli@linuxonhyperv.com
To: Stephen Hemminger <stephen@networkplumber.org>,
	Wei Hu <weh@microsoft.com>
Cc: dev@dpdk.org, Long Li <longli@microsoft.com>
Subject: [PATCH 0/4] Fix incorrect page size and address caclulations on systems with 64k (or other) page sizes
Date: Fri, 18 Apr 2025 12:32:46 -0700	[thread overview]
Message-ID: <1745004770-9795-1-git-send-email-longli@linuxonhyperv.com> (raw)

From: Long Li <longli@microsoft.com>

The Hyper-V uses 4k page size regardless of system page size.

This patchset fixes issues while running on systems with page sizes other than 4k.

Long Li (4):
  bus/vmbus: Align ring buffer data region to system page boundary
  bus/vmbus: Define Hyper-V page size
  bus/vmbus: Use Hyper-V page size for mapping to UIO pages
  net/netvsc: Use Hyper-V page size for the driver

 drivers/bus/vmbus/bus_vmbus_driver.h |  4 ++++
 drivers/bus/vmbus/linux/vmbus_uio.c  |  2 +-
 drivers/bus/vmbus/rte_vmbus_reg.h    |  9 +++------
 drivers/bus/vmbus/vmbus_bufring.c    |  9 ++++++---
 drivers/bus/vmbus/vmbus_common_uio.c |  2 +-
 drivers/net/netvsc/hn_rndis.c        | 14 +++++++-------
 drivers/net/netvsc/hn_rxtx.c         | 16 ++++++++--------
 drivers/net/netvsc/hn_var.h          |  4 ----
 8 files changed, 30 insertions(+), 30 deletions(-)

-- 
2.34.1


             reply	other threads:[~2025-04-18 19:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-18 19:32 longli [this message]
2025-04-18 19:32 ` [PATCH 1/4] bus/vmbus: Align ring buffer data region to system page boundary longli
2025-04-18 19:32 ` [PATCH 2/4] bus/vmbus: Define Hyper-V page size longli
2025-04-18 19:32 ` [PATCH 3/4] bus/vmbus: Use Hyper-V page size for mapping to UIO pages longli
2025-04-18 19:32 ` [PATCH 4/4] net/netvsc: Use Hyper-V page size for the driver longli

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=1745004770-9795-1-git-send-email-longli@linuxonhyperv.com \
    --to=longli@linuxonhyperv.com \
    --cc=dev@dpdk.org \
    --cc=longli@microsoft.com \
    --cc=stephen@networkplumber.org \
    --cc=weh@microsoft.com \
    /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).