From: Bruce Richardson <bruce.richardson@intel.com>
To: <dev@dpdk.org>
Subject: Re: [PATCH v4 0/2] net/ice: get link status updates via adminq message
Date: Wed, 4 Mar 2026 09:58:38 +0000 [thread overview]
Message-ID: <aagCToPf1Z1Z5N4i@bricha3-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <20260303162157.1634379-1-bruce.richardson@intel.com>
On Tue, Mar 03, 2026 at 04:21:55PM +0000, Bruce Richardson wrote:
> As explained in patch 2, change the link status tracking to be via receipt
> of an adminq message rather than directly querying the link status on
> interrupt. As part of this change, we can reduce the cost of using the
> adminq by removing the need to allocate and free memory but instead just
> use the stack to store any received adminq messages.
>
Recheck-request: loongarch-unit-testing
next prev parent reply other threads:[~2026-03-04 9:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 11:02 [PATCH] net/ice: get link status updates via adminq message Bruce Richardson
2026-02-27 11:41 ` [PATCH v2] " Bruce Richardson
2026-03-02 11:48 ` [PATCH v3 0/2] " Bruce Richardson
2026-03-02 11:48 ` [PATCH v3 1/2] net/ice: remove malloc call for admin queue msg Bruce Richardson
2026-03-02 11:48 ` [PATCH v3 2/2] net/ice: get link status updates via adminq message Bruce Richardson
2026-03-03 16:21 ` [PATCH v4 0/2] " Bruce Richardson
2026-03-03 16:21 ` [PATCH v4 1/2] net/ice: remove malloc call for admin queue msg Bruce Richardson
2026-03-04 11:59 ` Loftus, Ciara
2026-03-03 16:21 ` [PATCH v4 2/2] net/ice: get link status updates via adminq message Bruce Richardson
2026-03-04 11:56 ` Loftus, Ciara
2026-03-04 9:58 ` Bruce Richardson [this message]
2026-03-05 12:53 ` [PATCH v4 0/2] " David Marchand
2026-03-05 15:15 ` Bruce Richardson
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=aagCToPf1Z1Z5N4i@bricha3-mobl1.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=dev@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 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.