From: Nagaprabhanjan Bellaru <nagp.lists@gmail.com>
To: "Lu, Wenzhuo" <wenzhuo.lu@intel.com>
Cc: Ravi Kerur <rkerur@gmail.com>,
Thomas Monjalon <thomas.monjalon@6wind.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Not able to detect Intel EC I218-V (rev 03)
Date: Tue, 15 Mar 2016 20:02:23 +0530 [thread overview]
Message-ID: <CABDVJk_TMW8+b8BkRnEMxWrxbPCW7KFW0mfpAuoXEnt7FDtBJg@mail.gmail.com> (raw)
In-Reply-To: <6A0DE07E22DDAD4C9103DF62FEBC0909034361DD@shsmsx102.ccr.corp.intel.com>
Just for information, I have been using the patch on my laptop without
any issues so far..
Thanks,
-nagp
On Mon, Feb 29, 2016 at 6:24 AM, Lu, Wenzhuo <wenzhuo.lu@intel.com> wrote:
> Hi Thomas, Nagaprabhanjan,
>
> The base code has been updated, but some job is still left to support these
> NICs. Ravi has created a new patch set to complete it. Ravi can send it
> soon. Please wait a while and use the new patch set.
>
>
>
> Hi Ravi,
>
> As we talked, please send your patch to dpdk.org. Thanks a lot J
>
>
>
> Best regards
>
> Wenzhuo Lu
>
>
>
> From: Ravi Kerur [mailto:rkerur@gmail.com]
> Sent: Sunday, February 28, 2016 9:00 AM
> To: Thomas Monjalon
> Cc: Nagaprabhanjan Bellaru; Lu, Wenzhuo; users@dpdk.org
> Subject: Re: [dpdk-users] Not able to detect Intel EC I218-V (rev 03)
>
>
>
> Hi Thomas,
>
>
>
> I am working with Wenzhou on this patch since last week and the patch is now
> reviewed by Wenzhou. Let us know if we should resend the patch to dpdk.org?
>
>
>
> Thanks,
>
> Ravi
>
>
>
>
>
> On Sat, Feb 27, 2016 at 9:16 AM, Thomas Monjalon <thomas.monjalon@6wind.com>
> wrote:
>
> Hi,
>
> 2016-02-27 16:08, Nagaprabhanjan Bellaru:
>> I would be glad to do some testing, but I am just beginning to use DPDK,
>> can you please show me some pointers how to patch DPDK and then use it? I
>> could not find the files mentioned in the patch in the DPDK 2.2.0 suite
>> which I downloaded
>
> Maybe Ravi would be glad to help you offline to check this patch.
>
> Wenzhuo, we should try to integrate this patch please.
> Do you have some news explaining the delay for supporting this NIC?
>
>
>> On Sat, Feb 27, 2016 at 2:24 AM, Thomas Monjalon
>> <thomas.monjalon@6wind.com>
>> wrote:
>>
>> > Hi,
>> >
>> > 2016-02-26 18:59, Nagaprabhanjan Bellaru:
>> > > Hello,
>> > >
>> > > Using setup.sh (available in tools folder) I have bound eth0 (which is
>> > > of
>> > > Intel EC I218-V make) to igb_uio module (which I can see with
>> > > dpdk_nic_bind.py --status output):
>> > >
>> > > --
>> > > Network devices using DPDK-compatible driver
>> > > ============================================
>> > > 0000:00:19.0 'Ethernet Connection (3) I218-V' drv=igb_uio unused=
>> > >
>> > > Network devices using kernel driver
>> > > ===================================
>> > > <none>
>> > > --
>> > >
>> > > However, when I run any sample application, it complains that there
>> > > are
>> > no
>> > > ethernet ports:
>> > >
>> > > --
>> > > EAL: Error - exiting with code: 1
>> > > Cause: No available NIC ports!
>> > > --
>> > >
>> > > If I give a --vdev=eth_pcap0,iface=eth0, then it picks it. Am I
>> > > missing
>> > > something? I hope this Intel card is supported by DPDK.
>> >
>> > I think this card is not supported.
>> > We are waiting a review for this patch:
>> > http://dpdk.org/dev/patchwork/patch/7161/
>> > Do not hesitate to test it.
>> >
>
>
prev parent reply other threads:[~2016-03-15 14:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 13:29 Nagaprabhanjan Bellaru
2016-02-26 20:54 ` Thomas Monjalon
2016-02-27 10:38 ` Nagaprabhanjan Bellaru
2016-02-27 17:16 ` Thomas Monjalon
2016-02-28 0:59 ` Ravi Kerur
2016-02-29 0:54 ` Lu, Wenzhuo
2016-03-15 14:32 ` Nagaprabhanjan Bellaru [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=CABDVJk_TMW8+b8BkRnEMxWrxbPCW7KFW0mfpAuoXEnt7FDtBJg@mail.gmail.com \
--to=nagp.lists@gmail.com \
--cc=rkerur@gmail.com \
--cc=thomas.monjalon@6wind.com \
--cc=users@dpdk.org \
--cc=wenzhuo.lu@intel.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).