From: zhilong zheng <zhengzl0715@gmail.com>
To: Paul Tsvika <mozloverinweb@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] [dpdk][pktgen] - execute pktgen with mlx4 (40G) with some errors
Date: Mon, 31 Jul 2017 21:40:00 +0800 [thread overview]
Message-ID: <8EE90F16-6490-46AD-842C-E78F8DAA0F98@gmail.com> (raw)
In-Reply-To: <CAGi_MXmmAeknRVMU=ueNn7A+iJqyesbg2XUaEbkuNyjw82KcjA@mail.gmail.com>
No, you do not need any operation. This driver is bound to the device automatically.
> 在 2017年7月31日，21:25，Paul Tsvika <mozloverinweb@gmail.com> 写道：
>
> Sorry I am not with my testing machine now.
> if it uses mlx4_core, should I bind the device to the driver by using the following command?
>
> ./dpdk-devbind.py -b mlx4_core xx:xx.x
>
>
> Thanks
>
>
> P.T
>
> 2017-07-31 21:14 GMT+08:00 zhilong zheng <zhengzl0715@gmail.com <mailto:zhengzl0715@gmail.com>>:
> Yes, CX3 does not use igb_uio, it uses mlx4_core as the driver and you do not need to bind the device to igb_uio. Can you show the output when running command “./dpdk-devbind.py —status” and “ibstat"
>
>> 在 2017年7月31日，21:07，Paul Tsvika <mozloverinweb@gmail.com <mailto:mozloverinweb@gmail.com>> 写道：
>>
>> er I should
>
>
>
>
> --
> P.T
next prev parent reply other threads:[~2017-07-31 13:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 10:14 Paul Tsvika
2017-07-31 12:54 ` zhilong zheng
2017-07-31 13:07 ` Paul Tsvika
2017-07-31 13:14 ` zhilong zheng
2017-07-31 13:25 ` Paul Tsvika
2017-07-31 13:40 ` zhilong zheng [this message]
2017-07-31 14:00 ` Paul Tsvika
2017-07-31 16:11 ` Olga Shern
2017-08-01 3:38 ` Paul Tsvika
2017-08-01 4:15 ` zhilong zheng
2017-08-01 8:15 ` Paul Tsvika
2017-08-01 8:53 ` Zhilong Zheng
2017-08-01 9:04 ` Paul Tsvika
2017-08-01 9:12 ` Zhilong Zheng
2017-08-01 9:37 ` Paul Tsvika
2017-08-01 9:49 ` Zhilong Zheng
2017-08-01 14:05 ` Wiles, Keith
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=8EE90F16-6490-46AD-842C-E78F8DAA0F98@gmail.com \
--to=zhengzl0715@gmail.com \
--cc=mozloverinweb@gmail.com \
--cc=users@dpdk.org \
/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).