On 11/29/2013 04:39 PM, Thomas Monjalon wrote:
> 29/11/2013 13:25, Thomas Monjalon :
>
> Please check that your hardware do not support invariant TSC.
> It would explain why you need to fix frequency.
>
> I attach a simple code to test CPU feature "Invariant TSC".
I compiled and ran the code on al
Hmm, that's strange. I don't know how to interpret my observations then.
I have access to two platforms, one is based on Intel(R) Xeon(R) CPU
E3-1230 V2 @ 3.30GHz and another on Intel(R) Xeon(R) CPU E3-1270 v3 @
3.50GHz. Both running ubuntu-12.04 server. I see repeating errors on NIC
initialisa
29/11/2013 13:25, Thomas Monjalon :
> 29/11/2013 14:53, Dmitry Vyal :
> > On 11/28/2013 03:01 PM, Richardson, Bruce wrote:
> > > [BR] Frequency changes should not affect timers for modern Intel CPUs.
> > > Please see the " Intel(r) 64 and IA-32 Architectures Software
> > > Developer's
> > > Manual"
29/11/2013 14:53, Dmitry Vyal :
> On 11/28/2013 03:01 PM, Richardson, Bruce wrote:
> >> It's probably due to a frequency scaling.
> >> The timer based is initialized when DPDK initialize and the CPU can
> >> change
> >> its frequency, breaking next timers.
> >>
> >> The fix is to control the CPU f
Thomas29/11/2013 13:25, Monjalon :
> 29/11/2013 14:53, Dmitry Vyal :
> > On 11/28/2013 03:01 PM, Richardson, Bruce wrote:
> > > [BR] Frequency changes should not affect timers for modern Intel CPUs.
> >
> > The error frequency greatly reduces if I patch
> > loop limit as I described earlier or if
>
> It's probably due to a frequency scaling.
> The timer based is initialized when DPDK initialize and the CPU can change
> its frequency, breaking next timers.
>
> The fix is to control the CPU frequency.
> Please try this, without your patch:
> for g in /sys/devices/system/cpu/*/cpufreq/
Looks like I finally found the reason. After applying this patch I can
no longer reproduce the error.
diff --git a/lib/librte_pmd_ixgbe/ixgbe/ixgbe_82599.c
b/lib/librte_pmd_ixgbe/ixgbe/ixgbe_82599.c
index db07789..5f825fa 100644
--- a/lib/librte_pmd_ixgbe/ixgbe/ixgbe_82599.c
+++ b/lib/librte_pmd
I had exactly same problem and fixed it with same patch since release
1.4. But somehow it stopped to appear even without the patch. I have
no idea what I have done since both the kernel and the driver have
been updated during these days.
On Wed, Nov 27, 2013 at 4:06 PM, Dmitry Vyal wrote:
> Looks
27/11/2013 15:06, Dmitry Vyal :
> Looks like I finally found the reason. After applying this patch I can
> no longer reproduce the error.
>
> --- a/lib/librte_pmd_ixgbe/ixgbe/ixgbe_82599.c
> +++ b/lib/librte_pmd_ixgbe/ixgbe/ixgbe_82599.c
> /* Wait for AN to leave state 0 */
> - for
Hi, I'm experiencing weird problems with running dpdk examples on my
server running ubuntu-12.04. Application either manages to use ethernet
ports or doesn't. For example, this is results of two identical
sequental runs of l2fwd:
*
Hello,
22/11/2013 13:29, Dmitry Vyal :
> EAL: PCI device :02:00.0 on NUMA socket -1
> EAL: probe driver: 8086:10fb rte_ixgbe_pmd
> EAL: PCI memory mapped at 0x7f6b83687000
> EAL: PCI memory mapped at 0x7f6b83683000
> EAL: PCI device :02:00.1 on NUMA socket -1
> EAL: probe driver: 8
11 matches
Mail list logo
