* [dpdk-users] KNI drive without supported NICs? @ 2017-02-05 17:34 Lazarenko, Vlad (WorldQuant) 2017-02-06 11:05 ` Take Ceara 0 siblings, 1 reply; 4+ messages in thread From: Lazarenko, Vlad (WorldQuant) @ 2017-02-05 17:34 UTC (permalink / raw) To: 'users@dpdk.org' Gentlemen and gentleladies, I am trying to get the KNI working on my dev box. So I've loaded the rte_kni.ko module and made sure /dev/kni has correct permissions. But when I am trying to run the KNI example, it fails with "No supported Ethernet device found" error: $ build/kni -n 4 -c 0xf0 -- -P -p 0x3 --config="(0,4,6),(1,5,7)" EAL: Detected 24 lcore(s) EAL: PCI device 0000:01:00.0 on NUMA socket -1 EAL: probe driver: 8086:10d3 net_e1000_em EAL: Error - exiting with code: 1 Cause: No supported Ethernet device found My dev box does not in fact have supported NICs. But my understanding about KNI was that it allows to access Linux network stack trough the KNI kernel module, where applications create a virtual Ethernet devices (i.e. /sys/class/net/vEth*), thus there is no need for a real supported NIC or taking over the entire NIC. On the other hand, the example application calls rte_eth_dev_count() first, which in my case returns 0, and exits. Is my understanding about what KNI actually is wrong? Or am I missing something else? Thanks, Vlad ################################################################################### The information contained in this communication is confidential, may be subject to legal privilege, and is intended only for the individual named. If you are not the named addressee, please notify the sender immediately and delete this email from your system. The views expressed in this email are the views of the sender only. Outgoing and incoming electronic communications to this address are electronically archived and subject to review and/or disclosure to someone other than the recipient. ################################################################################### ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-users] KNI drive without supported NICs? 2017-02-05 17:34 [dpdk-users] KNI drive without supported NICs? Lazarenko, Vlad (WorldQuant) @ 2017-02-06 11:05 ` Take Ceara 2017-02-06 15:01 ` Lazarenko, Vlad (WorldQuant) 0 siblings, 1 reply; 4+ messages in thread From: Take Ceara @ 2017-02-06 11:05 UTC (permalink / raw) To: Lazarenko, Vlad (WorldQuant); +Cc: users Hi Vlad, On Sun, Feb 5, 2017 at 6:34 PM, Lazarenko, Vlad (WorldQuant) <Vlad.Lazarenko@worldquant.com> wrote: > Gentlemen and gentleladies, > > I am trying to get the KNI working on my dev box. So I've loaded the rte_kni.ko module and made sure /dev/kni has correct permissions. But when I am trying to run the KNI example, it fails with "No supported Ethernet device found" error: > > $ build/kni -n 4 -c 0xf0 -- -P -p 0x3 --config="(0,4,6),(1,5,7)" > EAL: Detected 24 lcore(s) > EAL: PCI device 0000:01:00.0 on NUMA socket -1 > EAL: probe driver: 8086:10d3 net_e1000_em > EAL: Error - exiting with code: 1 > Cause: No supported Ethernet device found > > My dev box does not in fact have supported NICs. But my understanding about KNI was that it allows to access Linux network stack trough the KNI kernel module, where applications create a virtual Ethernet devices (i.e. /sys/class/net/vEth*), thus there is no need for a real supported NIC or taking over the entire NIC. > > On the other hand, the example application calls rte_eth_dev_count() first, which in my case returns 0, and exits. > > Is my understanding about what KNI actually is wrong? Or am I missing something else? > As far as I know the KNI sample app actually forwards traffic to/from the kernel and a physical port therefore the check for physical interfaces. If you want to use KNI for something else there's nothing stopping you from starting a DPDK app and adding a KNI interface without having a real NIC bound to DPDK. I don't have a better example right now but, if you want, you can take a look at how we do it in warp17 (using DPDK) when you start it without any physical interfaces: https://github.com/Juniper/warp17#using-kernel-network-interface-kni-interfaces If you look at the HTTP example there we actually start the application without any physical interfaces (only one KNI): ./build/warp17 -c FC3 -n 4 -m 32768 -- --kni-ifs 1 > Thanks, > Vlad Hope this helps.. Regards, Dumitru > > > > ################################################################################### > > The information contained in this communication is confidential, may be > > subject to legal privilege, and is intended only for the individual named. > > If you are not the named addressee, please notify the sender immediately and > > delete this email from your system. The views expressed in this email are > > the views of the sender only. Outgoing and incoming electronic communications > > to this address are electronically archived and subject to review and/or disclosure > > to someone other than the recipient. > > ################################################################################### -- Dumitru Ceara ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-users] KNI drive without supported NICs? 2017-02-06 11:05 ` Take Ceara @ 2017-02-06 15:01 ` Lazarenko, Vlad (WorldQuant) 2017-02-13 10:12 ` Ferruh Yigit 0 siblings, 1 reply; 4+ messages in thread From: Lazarenko, Vlad (WorldQuant) @ 2017-02-06 15:01 UTC (permalink / raw) To: 'Take Ceara'; +Cc: users Dumitru, This clear things up a big time! Much appreciated. Thank you! - Vlad > -----Original Message----- > From: Take Ceara [mailto:dumitru.ceara@gmail.com] > Sent: Monday, February 06, 2017 6:05 AM > To: Lazarenko, Vlad (WorldQuant) > Cc: users@dpdk.org > Subject: Re: [dpdk-users] KNI drive without supported NICs? > > Hi Vlad, > > On Sun, Feb 5, 2017 at 6:34 PM, Lazarenko, Vlad (WorldQuant) > <Vlad.Lazarenko@worldquant.com> wrote: > > Gentlemen and gentleladies, > > > > I am trying to get the KNI working on my dev box. So I've loaded the > rte_kni.ko module and made sure /dev/kni has correct permissions. But > when I am trying to run the KNI example, it fails with "No supported > Ethernet device found" error: > > > > $ build/kni -n 4 -c 0xf0 -- -P -p 0x3 --config="(0,4,6),(1,5,7)" > > EAL: Detected 24 lcore(s) > > EAL: PCI device 0000:01:00.0 on NUMA socket -1 > > EAL: probe driver: 8086:10d3 net_e1000_em > > EAL: Error - exiting with code: 1 > > Cause: No supported Ethernet device found > > > > My dev box does not in fact have supported NICs. But my understanding > about KNI was that it allows to access Linux network stack trough the KNI > kernel module, where applications create a virtual Ethernet devices (i.e. > /sys/class/net/vEth*), thus there is no need for a real supported NIC or > taking over the entire NIC. > > > > On the other hand, the example application calls rte_eth_dev_count() > first, which in my case returns 0, and exits. > > > > Is my understanding about what KNI actually is wrong? Or am I missing > something else? > > > > As far as I know the KNI sample app actually forwards traffic to/from the > kernel and a physical port therefore the check for physical interfaces. If you > want to use KNI for something else there's nothing stopping you from > starting a DPDK app and adding a KNI interface without having a real NIC > bound to DPDK. > > I don't have a better example right now but, if you want, you can take a look > at how we do it in warp17 (using DPDK) when you start it without any > physical interfaces: > > https://github.com/Juniper/warp17#using-kernel-network-interface-kni- > interfaces > > If you look at the HTTP example there we actually start the application > without any physical interfaces (only one KNI): > > ./build/warp17 -c FC3 -n 4 -m 32768 -- --kni-ifs 1 > > > > Thanks, > > Vlad > > Hope this helps.. > > Regards, > Dumitru > > > > > > > > > > ################################################################### > ### > > ############# > > > > The information contained in this communication is confidential, may > > be > > > > subject to legal privilege, and is intended only for the individual named. > > > > If you are not the named addressee, please notify the sender > > immediately and > > > > delete this email from your system. The views expressed in this email > > are > > > > the views of the sender only. Outgoing and incoming electronic > > communications > > > > to this address are electronically archived and subject to review > > and/or disclosure > > > > to someone other than the recipient. > > > > > ################################################################### > ### > > ############# > > > > -- > Dumitru Ceara ################################################################################### The information contained in this communication is confidential, may be subject to legal privilege, and is intended only for the individual named. If you are not the named addressee, please notify the sender immediately and delete this email from your system. The views expressed in this email are the views of the sender only. Outgoing and incoming electronic communications to this address are electronically archived and subject to review and/or disclosure to someone other than the recipient. ################################################################################### ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [dpdk-users] KNI drive without supported NICs? 2017-02-06 15:01 ` Lazarenko, Vlad (WorldQuant) @ 2017-02-13 10:12 ` Ferruh Yigit 0 siblings, 0 replies; 4+ messages in thread From: Ferruh Yigit @ 2017-02-13 10:12 UTC (permalink / raw) To: Lazarenko, Vlad (WorldQuant), 'Take Ceara'; +Cc: users On 2/6/2017 3:01 PM, Lazarenko, Vlad (WorldQuant) wrote: > Dumitru, > > This clear things up a big time! Much appreciated. Thank you! KNI PMD patch [1], which is not upstream yet, can be used to create any number of KNI interfaces independent from hardware. It is a virtual PMD implementation, so can be used via testpmd or any DPDK application. [1] http://dpdk.org/dev/patchwork/patch/20092/ > > - Vlad > >> -----Original Message----- >> From: Take Ceara [mailto:dumitru.ceara@gmail.com] >> Sent: Monday, February 06, 2017 6:05 AM >> To: Lazarenko, Vlad (WorldQuant) >> Cc: users@dpdk.org >> Subject: Re: [dpdk-users] KNI drive without supported NICs? >> >> Hi Vlad, >> >> On Sun, Feb 5, 2017 at 6:34 PM, Lazarenko, Vlad (WorldQuant) >> <Vlad.Lazarenko@worldquant.com> wrote: >>> Gentlemen and gentleladies, >>> >>> I am trying to get the KNI working on my dev box. So I've loaded the >> rte_kni.ko module and made sure /dev/kni has correct permissions. But >> when I am trying to run the KNI example, it fails with "No supported >> Ethernet device found" error: >>> >>> $ build/kni -n 4 -c 0xf0 -- -P -p 0x3 --config="(0,4,6),(1,5,7)" >>> EAL: Detected 24 lcore(s) >>> EAL: PCI device 0000:01:00.0 on NUMA socket -1 >>> EAL: probe driver: 8086:10d3 net_e1000_em >>> EAL: Error - exiting with code: 1 >>> Cause: No supported Ethernet device found >>> >>> My dev box does not in fact have supported NICs. But my understanding >> about KNI was that it allows to access Linux network stack trough the KNI >> kernel module, where applications create a virtual Ethernet devices (i.e. >> /sys/class/net/vEth*), thus there is no need for a real supported NIC or >> taking over the entire NIC. >>> >>> On the other hand, the example application calls rte_eth_dev_count() >> first, which in my case returns 0, and exits. >>> >>> Is my understanding about what KNI actually is wrong? Or am I missing >> something else? >>> >> >> As far as I know the KNI sample app actually forwards traffic to/from the >> kernel and a physical port therefore the check for physical interfaces. If you >> want to use KNI for something else there's nothing stopping you from >> starting a DPDK app and adding a KNI interface without having a real NIC >> bound to DPDK. >> >> I don't have a better example right now but, if you want, you can take a look >> at how we do it in warp17 (using DPDK) when you start it without any >> physical interfaces: >> >> https://github.com/Juniper/warp17#using-kernel-network-interface-kni- >> interfaces >> >> If you look at the HTTP example there we actually start the application >> without any physical interfaces (only one KNI): >> >> ./build/warp17 -c FC3 -n 4 -m 32768 -- --kni-ifs 1 >> >> >>> Thanks, >>> Vlad >> >> Hope this helps.. >> >> Regards, >> Dumitru >> >>> >>> >>> >>> >> ################################################################### >> ### >>> ############# >>> >>> The information contained in this communication is confidential, may >>> be >>> >>> subject to legal privilege, and is intended only for the individual named. >>> >>> If you are not the named addressee, please notify the sender >>> immediately and >>> >>> delete this email from your system. The views expressed in this email >>> are >>> >>> the views of the sender only. Outgoing and incoming electronic >>> communications >>> >>> to this address are electronically archived and subject to review >>> and/or disclosure >>> >>> to someone other than the recipient. >>> >>> >> ################################################################### >> ### >>> ############# >> >> >> >> -- >> Dumitru Ceara > > > ################################################################################### > > The information contained in this communication is confidential, may be > > subject to legal privilege, and is intended only for the individual named. > > If you are not the named addressee, please notify the sender immediately and > > delete this email from your system. The views expressed in this email are > > the views of the sender only. Outgoing and incoming electronic communications > > to this address are electronically archived and subject to review and/or disclosure > > to someone other than the recipient. > > ################################################################################### > ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2017-02-13 10:12 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2017-02-05 17:34 [dpdk-users] KNI drive without supported NICs? Lazarenko, Vlad (WorldQuant) 2017-02-06 11:05 ` Take Ceara 2017-02-06 15:01 ` Lazarenko, Vlad (WorldQuant) 2017-02-13 10:12 ` Ferruh Yigit
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).