From: Lewis Donzis <lew@perftech.com>
To: Ferruh Yigit <ferruh.yigit@amd.com>
Cc: Bruce Richardson <bruce.richardson@intel.com>, dev <dev@dpdk.org>,
Jochen Behrens <jbehrens@vmware.com>,
Yong Wang <wang.yong19@zte.com.cn>,
"Xueming(Steven) Li" <xuemingl@nvidia.com>
Subject: Re: [PATCH] net/vmxnet3: fix use of interrupts on FreeBSD
Date: Wed, 24 Jan 2024 08:04:13 -0600 (CST) [thread overview]
Message-ID: <1801302770.16725699.1706105053781.JavaMail.zimbra@donzis.com> (raw)
In-Reply-To: <2e306a4a-1cb9-484b-b7f1-8ad9cd98986a@amd.com>
----- On Jan 24, 2024, at 7:58 AM, Ferruh Yigit ferruh.yigit@amd.com wrote:
> On 1/24/2024 12:34 PM, Lewis Donzis wrote:
>
>> ----- On Jan 11, 2024, at 6:03 AM, Ferruh Yigit ferruh.yigit@amd.com wrote:
>>
>>> On 1/9/2024 4:00 PM, Lewis Donzis wrote:
>>>>
>>>>
>>>> ----- On Jan 9, 2024, at 8:23 AM, Bruce Richardson bruce.richardson@intel.com
>>>> wrote:
>>>>
>>>>> DPDK does not support interrupts on FreeBSD, so the vmxnet3 driver
>>>>> returns error when enabling interrupts as it initializes. We can fix
>>>>> this by #ifdef'ing out the interrupt calls when building for FreeBSD,
>>>>> allowing the driver to initialize correctly.
>>>>>
>>>>> Fixes: 046f11619567 ("net/vmxnet3: support MSI-X interrupt")
>>>>>
>>>>> Reported-by: Lewis Donzis <lew@perftech.com>
>>>>> Signed-off-by: Bruce Richardson <bruce.richardson@intel.com>
>>>>>>
>>>> Tested-by: Lewis Donzis <lew@perftech.com>
>>>>
>>>
>>> Acked-by: Ferruh Yigit <ferruh.yigit@amd.com>
>>>
>>> Applied to dpdk-next-net/main, thanks.
>>
>> Did this get checked in?
>>
>> Just curious because I don't see it in 22.11.4 that was released
> yesterday, so wasn't sure when it would show up.
>>
>>
>
> Hi Lew,
>
> It has been merged into the 'next-net' subtree and will be subsequently
> pulled into the 'main' tree. Eventually, it will be included in the
> 24.03 release.
>
> LTS releases will backport the fix after the release of v24.03.
>
> If you are interested in 22.11.# LTS, this fix is expected to be
> included in v22.11.5 scheduled for release in April."
Perfect, thanks very much for the explanation.
lew
prev parent reply other threads:[~2024-01-24 14:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-29 20:45 vmxnet3 no longer functional on DPDK 21.11 Lewis Donzis
2021-11-30 8:53 ` Ferruh Yigit
2021-11-30 13:42 ` Bruce Richardson
2021-12-06 1:52 ` Lewis Donzis
2021-12-06 9:16 ` Bruce Richardson
2021-12-06 12:08 ` Ananyev, Konstantin
2021-12-06 13:58 ` Lewis Donzis
2022-06-03 13:19 ` Lewis Donzis
2022-06-03 15:25 ` Ferruh Yigit
2024-01-06 14:50 ` Lewis Donzis
2024-01-09 10:21 ` Bruce Richardson
2024-01-09 13:46 ` Lewis Donzis
2024-01-09 14:28 ` Bruce Richardson
2024-01-09 15:21 ` Lewis Donzis
2024-01-09 15:35 ` Bruce Richardson
2024-01-09 23:55 ` Stephen Hemminger
2024-01-10 13:36 ` Lewis Donzis
2024-01-09 14:23 ` [PATCH] net/vmxnet3: fix use of interrupts on FreeBSD Bruce Richardson
2024-01-09 16:00 ` Lewis Donzis
2024-01-11 12:03 ` Ferruh Yigit
2024-01-24 12:34 ` Lewis Donzis
2024-01-24 13:58 ` Ferruh Yigit
2024-01-24 14:04 ` Lewis Donzis [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=1801302770.16725699.1706105053781.JavaMail.zimbra@donzis.com \
--to=lew@perftech.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jbehrens@vmware.com \
--cc=wang.yong19@zte.com.cn \
--cc=xuemingl@nvidia.com \
/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).