From: Stephen Hemminger <stephen@networkplumber.org>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: "Ferruh Yigit" <ferruh.yigit@amd.com>,
"Michał Krawczyk" <mk@semihalf.com>,
"William Tu" <u9012063@gmail.com>, dpdk-dev <dev@dpdk.org>,
"Igor Chauskin" <igorch@amazon.com>,
"Evgeny Schemeilin" <evgenys@amazon.com>,
"Shai Brandes" <shaibran@amazon.com>,
"Marcin Wojtas" <mw@semihalf.com>,
"Narcisa Ana Maria Vasile" <navasile@linux.microsoft.com>,
"Dmitry Malloy" <dmitrym@microsoft.com>,
"Pallavi Kadam" <pallavi.kadam@intel.com>
Subject: Re: [dpdk-dev] [PATCH RFC] net/ena: Add Windows support.
Date: Thu, 10 Aug 2023 08:47:55 -0700 [thread overview]
Message-ID: <20230810084755.2ac50b8a@hermes.local> (raw)
In-Reply-To: <20230323171955.06c8fc24@sovereign>
On Thu, 23 Mar 2023 17:19:55 +0300
Dmitry Kozlyuk <dmitry.kozliuk@gmail.com> wrote:
> > >> This is a very old thread, but still in the patchwork, I wonder if is
> > >> there any update on the issue?
> > >
> > > Hi Ferruh,
> > >
> > > sorry for the late reply - nothing new from my side.
> > >
> > > I'm not sure what's the current state of the netuio interrupt support
> > > for the Windows, but if it still didn't land, then the original issue
> > > still persists.
> > >
> >
> > Hi William, Dmitry,
> >
> > Is there any update on the netuio interrupt support?
> > What is the plan for this patch?
>
> Hi Ferruh,
>
> The work on the interrupt support has been abandoned unfortunately.
> I'd like to complete it one day, but can't make a commitment right now.
>
> Ref:
> http://patchwork.dpdk.org/project/dpdk/patch/20211012011107.431188-1-dmitry.kozliuk@gmail.com/
Marking this patch as "Awaiting upstream" since it depends on interrupt
support in Windows which is not available.
prev parent reply other threads:[~2023-08-10 15:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 3:36 William Tu
2021-08-14 11:31 ` Dmitry Kozlyuk
2021-08-14 15:37 ` William Tu
2021-08-19 2:19 ` William Tu
2021-08-30 7:11 ` Michał Krawczyk
2021-08-30 14:05 ` William Tu
2022-05-20 22:08 ` Ferruh Yigit
2022-06-06 7:53 ` Michał Krawczyk
2023-03-23 13:13 ` Ferruh Yigit
2023-03-23 14:19 ` Dmitry Kozlyuk
2023-08-10 15:47 ` Stephen Hemminger [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=20230810084755.2ac50b8a@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=evgenys@amazon.com \
--cc=ferruh.yigit@amd.com \
--cc=igorch@amazon.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.com \
--cc=navasile@linux.microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=shaibran@amazon.com \
--cc=u9012063@gmail.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).