From: Ferruh Yigit <ferruh.yigit@amd.com>
To: Tom Jones <thj@freebsd.org>, dev@dpdk.org
Cc: stable@dpdk.org, David Marchand <david.marchand@redhat.com>
Subject: Re: [PATCH] net/vmxnet3: Don't enable rx queue interrupts on FreeBSD
Date: Thu, 21 Mar 2024 14:30:38 +0000 [thread overview]
Message-ID: <67028d9d-39d0-4ec0-aa27-1e5d31d7a6ea@amd.com> (raw)
In-Reply-To: <20240321103133.1531-1-thj@freebsd.org>
On 3/21/2024 10:31 AM, Tom Jones wrote:
> Commit 29a1c9107bb disabled interrupts on FreeBSD for the vmxnet3 driver
> as they are not supported. Rx queue interrupts were missed by this
> change, don't attempt to enable them on FreeBSD.
>
> Without this change applications enabling interrupts encounter an
> immediate abort on FreeBSD.
>
> Fixes: 40d5676ff1ea ("net/vmxnet3: fix initialization on FreeBSD")
> Cc: stable@dpdk.org
>
> Signed-off-by: Tom Jones <thj@freebsd.org>
>
Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
Applied to dpdk-next-net/main, thanks.
(
- Commit log updated slightly, removed "Commit 29a1c9107bb" references
- updated .mailmap
)
prev parent reply other threads:[~2024-03-21 14:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240320130255.1526-1-thj@freebsd.org>
2024-03-21 10:31 ` Tom Jones
2024-03-21 14:30 ` 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=67028d9d-39d0-4ec0-aa27-1e5d31d7a6ea@amd.com \
--to=ferruh.yigit@amd.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=thj@freebsd.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).