DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: William Tu <u9012063@gmail.com>
Cc: dev <dev@dpdk.org>, Dmitry Kozlyuk <Dmitry.Kozliuk@gmail.com>,
	 Pallavi Kadam <pallavi.kadam@intel.com>,
	"Wang, Haiyue" <haiyue.wang@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/e1000: build on Windows
Date: Fri, 8 Oct 2021 14:24:18 +0200	[thread overview]
Message-ID: <CAJFAV8wL2hRXkTY3ujExXCNk5AGejcPw4WWb4Drsq=LDW1ONoQ@mail.gmail.com> (raw)
In-Reply-To: <CALDO+SbZs=Er21bH_MWbassM4oaD-GTUZByT_aBU90C4w8-iSg@mail.gmail.com>

On Fri, Oct 8, 2021 at 2:21 PM William Tu <u9012063@gmail.com> wrote:
> > > Example when running:
> > > PS C:\dpdk> .\build\app\dpdk-testpmd.exe
> > > EAL: Detected CPU lcores: 4
> > > EAL: Detected NUMA nodes: 1
> > > EAL: Multi-process support is requested, but not available.
> > > EAL: WARNING: TSC frequency estimated roughly - clock timings may be less accurate.
> > > EAL: Probe PCI driver: net_e1000_em (8086:10d3) device: 0000:03:00.0 (socket 0)
> > > EAL: Requested device 0000:1b:00.0 cannot be used
> >
> > Odd to read this, and still see testpmd getting one port afterwards.
> This is expected. Because I only enable 1 dpdk port (0000:03:00.0)
> The 0000:1b:00.0 is still running kernel driver. I will mention it in next
> version.

Ok sorry, I did not notice.
No need to mention, simply start testpmd with -a 0000:03:00.0.


-- 
David Marchand


  reply	other threads:[~2021-10-08 12:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07 20:24 William Tu
2021-10-08  6:54 ` David Marchand
2021-10-08  6:55   ` David Marchand
2021-10-08 12:20   ` William Tu
2021-10-08 12:24     ` David Marchand [this message]
2021-10-08 13:53 ` [dpdk-dev] [PATCH v2] " William Tu
2021-10-08 16:08   ` Wang, Haiyue
2021-10-08 21:12     ` Kadam, Pallavi
2021-10-08 20:35   ` Dmitry Kozlyuk
2021-10-08 21:41     ` William Tu
2021-10-09 16:37     ` William Tu
2021-10-09  0:02   ` Kadam, Pallavi
2021-10-09  0:14     ` William Tu
2021-10-09 18:40       ` Kadam, Pallavi
2021-10-09 16:31   ` [dpdk-dev] [PATCH v3] " William Tu
2021-10-09 17:28     ` Dmitry Kozlyuk
2021-10-10 10:56       ` Wang, Haiyue
2021-10-19 19:05     ` William Tu
2021-10-19 19:12       ` Thomas Monjalon
2021-10-20  3:47     ` [dpdk-dev] [PATCH v4] " William Tu
2021-10-21  2:56       ` Zhang, Qi Z

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='CAJFAV8wL2hRXkTY3ujExXCNk5AGejcPw4WWb4Drsq=LDW1ONoQ@mail.gmail.com' \
    --to=david.marchand@redhat.com \
    --cc=Dmitry.Kozliuk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=haiyue.wang@intel.com \
    --cc=pallavi.kadam@intel.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).