On 27-Aug-19 1:48 PM, Bruce Richardson wrote:
On Tue, Aug 27, 2019 at 01:04:18PM +0100, Burakov, Anatoly wrote:
On 26-Aug-19 2:44 PM, Jim Harris wrote:
Ideally, get_tsc_freq_arch() is able to provide the
TSC rate using arch-specific means. When that is not
possible, DPDK reverts to calculating
On Tue, Aug 27, 2019 at 01:04:18PM +0100, Burakov, Anatoly wrote:
> On 26-Aug-19 2:44 PM, Jim Harris wrote:
> > Ideally, get_tsc_freq_arch() is able to provide the
> > TSC rate using arch-specific means. When that is not
> > possible, DPDK reverts to calculating the TSC rate with
> > a 100ms nanos
On Tue, Aug 27, 2019 at 01:04:18PM +0100, Burakov, Anatoly wrote:
> On 26-Aug-19 2:44 PM, Jim Harris wrote:
> > Ideally, get_tsc_freq_arch() is able to provide the
> > TSC rate using arch-specific means. When that is not
> > possible, DPDK reverts to calculating the TSC rate with
> > a 100ms nanos
On 26-Aug-19 2:44 PM, Jim Harris wrote:
Ideally, get_tsc_freq_arch() is able to provide the
TSC rate using arch-specific means. When that is not
possible, DPDK reverts to calculating the TSC rate with
a 100ms nanosleep or 1s sleep. The latter occurs more
frequently in VMs which often do not hav
On Mon, Aug 26, 2019 at 06:44:46AM -0700, Jim Harris wrote:
> Ideally, get_tsc_freq_arch() is able to provide the
> TSC rate using arch-specific means. When that is not
> possible, DPDK reverts to calculating the TSC rate with
> a 100ms nanosleep or 1s sleep. The latter occurs more
> frequently i
Ideally, get_tsc_freq_arch() is able to provide the
TSC rate using arch-specific means. When that is not
possible, DPDK reverts to calculating the TSC rate with
a 100ms nanosleep or 1s sleep. The latter occurs more
frequently in VMs which often do not have access to the
data they need from arch-s
6 matches
Mail list logo