From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Jiawen Wu <jiawenwu@trustnetic.com>
Cc: stable@dpdk.org, dev@dpdk.org
Subject: Re: [PATCH v2] net/txgbe: fix blocking system events
Date: Fri, 30 Jun 2023 11:03:50 +0100 [thread overview]
Message-ID: <86a963f0-ad0c-97a5-5b1f-e84f4471b472@amd.com> (raw)
In-Reply-To: <20230630093512.314184-1-jiawenwu@trustnetic.com>
On 6/30/2023 10:35 AM, Jiawen Wu wrote:
> Refer to commit 819d0d1d57f1 ("net/ixgbe: fix blocking system events").
> Fix the same issue as ixgbe.
>
> TXGBE link status task uses rte alarm thread in old implementation.
> Sometime txgbe link status task takes up to 9 seconds. This will
> severely affect the rte-alarm-thread dependent tasks in the
> system, like interrupt or hotplug event. So replace with an
> independent thread which has the same thread affinity settings
> as rte interrupt.
>
> Fixes: 0c061eadec59 ("net/txgbe: add link status change")
> Cc: stable@dpdk.org
>
> Signed-off-by: Jiawen Wu <jiawenwu@trustnetic.com>
>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2023-06-30 10:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-29 10:07 [PATCH] " Jiawen Wu
2023-06-29 14:20 ` Ferruh Yigit
2023-06-30 9:35 ` [PATCH v2] " Jiawen Wu
2023-06-30 10:03 ` Ferruh Yigit [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=86a963f0-ad0c-97a5-5b1f-e84f4471b472@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=jiawenwu@trustnetic.com \
--cc=stable@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).