From: Shai Brandes <shaibran@amazon.com>
To: <stephen@networkplumber.org>
Cc: <dev@dpdk.org>, Shai Brandes <shaibran@amazon.com>
Subject: [PATCH 07/13] net/ena/base: deduplicate LLQ entry write and advance
Date: Tue, 13 Oct 2026 18:09:30 +0300 [thread overview]
Message-ID: <20261013150930.9580-1-shaibran@amazon.com> (raw)
ena_com_close_llq_entry() and ena_com_sq_update_llq_tail() duplicate
the same sequence for flushing the current LLQ entry to the device and
moving on to the next one: write the bounce buffer, fetch the next
bounce buffer and reset it.
Extract the common sequence into a new helper,
ena_com_write_and_advance_llq_entry(), and call it from both sites.
No functional change.
Signed-off-by: Shai Brandes <shaibran@amazon.com>
---
drivers/net/ena/base/ena_eth_com.c | 49 ++++++++++++++++--------------
1 file changed, 27 insertions(+), 22 deletions(-)
diff --git a/drivers/net/ena/base/ena_eth_com.c b/drivers/net/ena/base/ena_eth_com.c
index e3b2a753c4..ca15306859 100644
--- a/drivers/net/ena/base/ena_eth_com.c
+++ b/drivers/net/ena/base/ena_eth_com.c
@@ -204,6 +204,29 @@ static void *get_sq_desc_llq(struct ena_com_io_sq *io_sq)
return sq_desc;
}
+static int ena_com_write_and_advance_llq_entry(struct ena_com_io_sq *io_sq)
+{
+ struct ena_com_llq_pkt_ctrl *pkt_ctrl = &io_sq->llq_buf_ctrl;
+ struct ena_com_llq_info *llq_info = &io_sq->llq_info;
+ int rc;
+
+ rc = ena_com_write_bounce_buffer_to_dev(io_sq,
+ pkt_ctrl->curr_llq_entry);
+ if (unlikely(rc)) {
+ ena_trc_err(ena_com_io_sq_to_ena_dev(io_sq),
+ "Failed to write bounce buffer to device\n");
+ return rc;
+ }
+
+ pkt_ctrl->curr_llq_entry =
+ ena_com_get_next_bounce_buffer(&io_sq->bounce_buf_ctrl);
+
+ memset(io_sq->llq_buf_ctrl.curr_llq_entry,
+ 0x0, llq_info->desc_list_entry_size);
+
+ return ENA_COM_OK;
+}
+
static int ena_com_close_llq_entry(struct ena_com_io_sq *io_sq)
{
struct ena_com_llq_pkt_ctrl *pkt_ctrl = &io_sq->llq_buf_ctrl;
@@ -215,18 +238,9 @@ static int ena_com_close_llq_entry(struct ena_com_io_sq *io_sq)
/* bounce buffer was used, so write it and get a new one */
if (likely(pkt_ctrl->idx)) {
- rc = ena_com_write_bounce_buffer_to_dev(io_sq,
- pkt_ctrl->curr_llq_entry);
- if (unlikely(rc)) {
- ena_trc_err(ena_com_io_sq_to_ena_dev(io_sq),
- "Failed to write bounce buffer to device\n");
+ rc = ena_com_write_and_advance_llq_entry(io_sq);
+ if (unlikely(rc))
return rc;
- }
-
- pkt_ctrl->curr_llq_entry =
- ena_com_get_next_bounce_buffer(&io_sq->bounce_buf_ctrl);
- memset(io_sq->llq_buf_ctrl.curr_llq_entry,
- 0x0, llq_info->desc_list_entry_size);
}
pkt_ctrl->idx = 0;
@@ -258,18 +272,9 @@ static int ena_com_sq_update_llq_tail(struct ena_com_io_sq *io_sq)
int rc;
if (!pkt_ctrl->descs_left_in_line) {
- rc = ena_com_write_bounce_buffer_to_dev(io_sq,
- pkt_ctrl->curr_llq_entry);
- if (unlikely(rc)) {
- ena_trc_err(ena_com_io_sq_to_ena_dev(io_sq),
- "Failed to write bounce buffer to device\n");
+ rc = ena_com_write_and_advance_llq_entry(io_sq);
+ if (unlikely(rc))
return rc;
- }
-
- pkt_ctrl->curr_llq_entry =
- ena_com_get_next_bounce_buffer(&io_sq->bounce_buf_ctrl);
- memset(io_sq->llq_buf_ctrl.curr_llq_entry,
- 0x0, llq_info->desc_list_entry_size);
pkt_ctrl->idx = 0;
pkt_ctrl->descs_left_in_line = llq_info->descs_per_entry;
--
2.17.1
reply other threads:[~2026-10-13 15:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261013150930.9580-1-shaibran@amazon.com \
--to=shaibran@amazon.com \
--cc=dev@dpdk.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox