[dpdk-dev] [RFC 1/7] eal/common: define rte_soc_* related common interface

2016-01-02 Thread Stephen Hemminger
On Fri, 1 Jan 2016 22:05:20 +0100 Jan Viktorin wrote: > Introduce the interface to SoC device infrastructure. A SoC device > here means a device integrated on the chip via a (simple) bus > that lacks of auto-discovery and other properties which are common > for PCI. A counterpart in the Linux Ke

[dpdk-dev] [RFC 1/7] eal/common: define rte_soc_* related common interface

2016-01-02 Thread Wiles, Keith
On 1/2/16, 12:01 PM, "dev on behalf of Stephen Hemminger" wrote: >On Fri, 1 Jan 2016 22:05:20 +0100 >Jan Viktorin wrote: > >> Introduce the interface to SoC device infrastructure. A SoC device >> here means a device integrated on the chip via a (simple) bus >> that lacks of auto-discovery and o

[dpdk-dev] [RFC 1/7] eal/common: define rte_soc_* related common interface

2016-01-02 Thread Jan Viktorin
On Sat, 2 Jan 2016 10:01:44 -0800 Stephen Hemminger wrote: > On Fri, 1 Jan 2016 22:05:20 +0100 > Jan Viktorin wrote: > > > Introduce the interface to SoC device infrastructure. A SoC device > > here means a device integrated on the chip via a (simple) bus > > that lacks of auto-discovery and o

[dpdk-dev] [RFC 1/7] eal/common: define rte_soc_* related common interface

2016-01-02 Thread Jan Viktorin
On Sat, 2 Jan 2016 18:35:08 + "Wiles, Keith" wrote: > >Yes, DPDK needs to work in embedded environments with device tree. > >Would it be possible reimplement device tree parsing in user space? > >Ideally with a shared code from kernel?? > > Stephen, Do you mean we have to add kernel code t

[dpdk-dev] [RFC 1/7] eal/common: define rte_soc_* related common interface

2016-01-02 Thread Wiles, Keith
On 1/2/16, 12:52 PM, "Jan Viktorin" wrote: >On Sat, 2 Jan 2016 18:35:08 + >"Wiles, Keith" wrote: > >> >Yes, DPDK needs to work in embedded environments with device tree. >> >Would it be possible reimplement device tree parsing in user space? >> >Ideally with a shared code from kernel?? >>

[dpdk-dev] [RFC 1/7] eal/common: define rte_soc_* related common interface

2016-01-02 Thread Stephen Hemminger
On Sat, 2 Jan 2016 19:52:16 +0100 Jan Viktorin wrote: > On Sat, 2 Jan 2016 18:35:08 + > "Wiles, Keith" wrote: > > > >Yes, DPDK needs to work in embedded environments with device tree. > > >Would it be possible reimplement device tree parsing in user space? > > >Ideally with a shared code fr

[dpdk-dev] [RFC 1/7] eal/common: define rte_soc_* related common interface

2016-01-02 Thread Wiles, Keith
On 1/2/16, 1:14 PM, "Stephen Hemminger" wrote: >On Sat, 2 Jan 2016 19:52:16 +0100 >Jan Viktorin wrote: > >> On Sat, 2 Jan 2016 18:35:08 + >> "Wiles, Keith" wrote: >> >> > >Yes, DPDK needs to work in embedded environments with device tree. >> > >Would it be possible reimplement device tree

[dpdk-dev] librte_power w/ intel_pstate cpufreq governor

2016-01-02 Thread Matthew Hall
Hello, In about one month, I never received any response about all these major issues I was finding with librte_power and the intel_pstate based CPU clockrate control driver used in all the new Linux kernels. From what I can tell, none of this librte_power code ever worked right in the first