DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Michał Krawczyk" <mk@semihalf.com>
To: William Tu <u9012063@gmail.com>
Cc: Dmitry Kozlyuk <dmitry.kozliuk@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>
Subject: Re: [dpdk-dev] [PATCH RFC] net/ena: Add Windows support.
Date: Mon, 30 Aug 2021 09:11:57 +0200	[thread overview]
Message-ID: <CAJMMOfNqZeMJYvfdzFdKMeirchsxjRBQiY-DUkwP3vzA_+P8zw@mail.gmail.com> (raw)
In-Reply-To: <CALDO+SYd+BC04oicST8x-_ZRH_yKcKe70Zk4_YS0aA410dHFFQ@mail.gmail.com>

czw., 19 sie 2021 o 04:19 William Tu <u9012063@gmail.com> napisał(a):
>
> So I finally set up everything on AWS and tested this patch.
> Virt2phys and netuio (I added ena conf) load OK.
> Finally, starting dpdk-testpmd, I got some errors below:
> ---
> PS C:\dpdk-kmods> cd c:\dpdk
> PS C:\dpdk> .\build\app\dpdk-testpmd.exe
> EAL: Detected 4 lcore(s)
> EAL: Detected 1 NUMA nodes
> EAL: Multi-process support is requested, but not available.
> EAL: WARNING: TSC frequency estimated roughly - clock timings may be
> less accurate.
> EAL: Requested device 0000:00:05.0 cannot be used
> EAL: Probe PCI driver: net_ena (1d0f:ec20) device: 0000:00:06.0 (socket 0)
> EAL: eth_ena_pci_probe[ENA_COM:
> ena_com_wait_and_process_admin_cq_interrupts]Invalid wait event.
> pthread ret: 1
> [ENA_COM: ena_com_wait_and_process_admin_cq_interrupts]The ena device
> sent a completion but the driver didn
> 't receive a MSI-X interrupt (cmd 9), autopolling mode is OFF
> [ENA_COM: ena_com_set_dev_mtu]Failed to set mtu 1500. error: -137
> ena_mtu_set(): Could not set MTU: 1500
> Failed to set MTU to 1500 for port 0
> testpmd: create a new mbuf pool <mb_pool_0>: n=171456, size=2176, socket=0
> testpmd: preferred mempool ops selected: ring_mp_mc
>
> Warning! port-topology=paired and odd forward ports number, the last
> port will pair with itself.
>
> Configuring Port 0 (socket 0)
> [ENA_COM: ena_com_create_io_cq]Failed to create IO CQ. error: -19
> ena_create_io_queue(): Failed to create IO queue[0] (qid:1), rc: -19
> ena_queue_start(): Failed to create IO queue
> ena_queue_start_all(): Failed to start queue[0] of type(1)
> Fail to start port 0: No such device
> Please stop the ports first
> Done
> Error during enabling promiscuous mode for port 0: Unknown error - ignore
> No commandline core given, start packet forwarding
> Not all ports were started
> ---
> I will see if I can fix these issues and I will submit v2 patch.
> Thanks

Hi William,

It's great to hear that you're working on ENA support for Windows!

ENA PMD uses admin interrupt for processing all the commands like
creating the IO queues, setting up the MTU, etc., and also for the
AENQ events. With the current driver design it's critical to have this
admin interrupt working.

It looks like the admin interrupt is not functional and from what I've
seen in the email regarding the v21.11 roadmap for the Windows
support, the netuio interrupt support is going to be added in the
future. That might be the reason for you seeing those errors.

Thanks,
Michal

> William

  reply	other threads:[~2021-08-30  7:12 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 [this message]
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

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=CAJMMOfNqZeMJYvfdzFdKMeirchsxjRBQiY-DUkwP3vzA_+P8zw@mail.gmail.com \
    --to=mk@semihalf.com \
    --cc=dev@dpdk.org \
    --cc=dmitry.kozliuk@gmail.com \
    --cc=evgenys@amazon.com \
    --cc=igorch@amazon.com \
    --cc=mw@semihalf.com \
    --cc=navasile@linux.microsoft.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).