All of lore.kernel.org
 help / color / mirror / Atom feed
From: Serhii Iliushyk <sil-plv@napatech.com>
To: stephen@networkplumber.org, mko-plv@napatech.com, ckm@napatech.com
Cc: dev@dpdk.org
Subject: [PATCH v1 1/3] net/ntnic: remove unused unmanaged virt queue setup ops
Date: Tue,  8 Sep 2026 18:27:22 +0200	[thread overview]
Message-ID: <20260908162724.463767-2-sil-plv@napatech.com> (raw)
In-Reply-To: <20260908162724.463767-1-sil-plv@napatech.com>

The unmanaged Rx/Tx virt queue setup ops have never had a caller;
only the managed variants are used. Drop them in preparation for
allocating the queue state per queue.

Signed-off-by: Serhii Iliushyk <sil-plv@napatech.com>
---
 drivers/net/ntnic/dbsconfig/ntnic_dbsconfig.c |  2 --
 drivers/net/ntnic/ntnic_mod_reg.h             | 30 -------------------
 2 files changed, 32 deletions(-)

diff --git a/drivers/net/ntnic/dbsconfig/ntnic_dbsconfig.c b/drivers/net/ntnic/dbsconfig/ntnic_dbsconfig.c
index 56eb710d25..7c10acb4e2 100644
--- a/drivers/net/ntnic/dbsconfig/ntnic_dbsconfig.c
+++ b/drivers/net/ntnic/dbsconfig/ntnic_dbsconfig.c
@@ -1432,8 +1432,6 @@ static void nthw_release_tx_packets(struct nthw_virt_queue *txvq, uint16_t n, ui
 }
 
 static struct sg_ops_s sg_ops = {
-	.nthw_setup_rx_virt_queue = nthw_setup_rx_virt_queue,
-	.nthw_setup_tx_virt_queue = nthw_setup_tx_virt_queue,
 	.nthw_setup_mngd_rx_virt_queue = nthw_setup_mngd_rx_virt_queue,
 	.nthw_release_mngd_rx_virt_queue = nthw_release_mngd_rx_virt_queue,
 	.nthw_setup_mngd_tx_virt_queue = nthw_setup_mngd_tx_virt_queue,
diff --git a/drivers/net/ntnic/ntnic_mod_reg.h b/drivers/net/ntnic/ntnic_mod_reg.h
index 81ba1e44f9..1b5047b3dd 100644
--- a/drivers/net/ntnic/ntnic_mod_reg.h
+++ b/drivers/net/ntnic/ntnic_mod_reg.h
@@ -24,36 +24,6 @@
 
 /* sg ops section */
 struct sg_ops_s {
-	/* Setup a virtQueue for a VM */
-	struct nthw_virt_queue *(*nthw_setup_rx_virt_queue)(nthw_dbs_t *p_nthw_dbs,
-		uint32_t index,
-		uint16_t start_idx,
-		uint16_t start_ptr,
-		void *avail_struct_phys_addr,
-		void *used_struct_phys_addr,
-		void *desc_struct_phys_addr,
-		uint16_t queue_size,
-		uint32_t host_id,
-		uint32_t header,
-		uint32_t vq_type,
-		int irq_vector,
-		uint8_t rx_deferred_start);
-	struct nthw_virt_queue *(*nthw_setup_tx_virt_queue)(nthw_dbs_t *p_nthw_dbs,
-		uint32_t index,
-		uint16_t start_idx,
-		uint16_t start_ptr,
-		void *avail_struct_phys_addr,
-		void *used_struct_phys_addr,
-		void *desc_struct_phys_addr,
-		uint16_t queue_size,
-		uint32_t host_id,
-		uint32_t port,
-		uint32_t virtual_port,
-		uint32_t header,
-		uint32_t vq_type,
-		int irq_vector,
-		uint32_t in_order,
-		uint8_t tx_deferred_start);
 	struct nthw_virt_queue *(*nthw_setup_mngd_rx_virt_queue)(nthw_dbs_t *p_nthw_dbs,
 		uint32_t index,
 		uint32_t queue_size,
-- 
2.45.0


  reply	other threads:[~2026-09-08 16:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-08 16:27 [PATCH v1 0/3] net/ntnic: fix virt queue data in BSS Serhii Iliushyk
2026-09-08 16:27 ` Serhii Iliushyk [this message]
2026-09-08 16:27 ` [PATCH v1 2/3] net/ntnic: check virt queue hardware setup result Serhii Iliushyk
2026-09-08 16:27 ` [PATCH v1 3/3] net/ntnic: fix virt queue data in BSS Serhii Iliushyk
2026-09-08 17:18 ` [PATCH v1 0/3] " Stephen Hemminger

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=20260908162724.463767-2-sil-plv@napatech.com \
    --to=sil-plv@napatech.com \
    --cc=ckm@napatech.com \
    --cc=dev@dpdk.org \
    --cc=mko-plv@napatech.com \
    --cc=stephen@networkplumber.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.