On Fri, Sep 29, 2017 at 8:23 PM, Pete French wrote:
>> Hmm, by ntpd I think you mean ntp client? You will have to disable
>> timesync if you run ntp client:
>> sysctl hw.hvtimesync.sample_thresh=-1
>> sysctl hw.hvtimesync.ignore_sync=1
>>
>> They interfere w/ each other.
>
> Oh! Does this apply t
On Fri, Sep 29, 2017 at 12:36 PM, Paul Koch wrote:
> On Thu, 14 Sep 2017 09:54:56 +0800
> Sepherosa Ziehau wrote:
>
>> If you have any updates on this, please let me know. There is still
>> time for 10.4.
>
> We are still playing around with this in the lab...
>
If you have any updates on this, please let me know. There is still
time for 10.4.
On Thu, Sep 7, 2017 at 11:04 PM, Paul Koch wrote:
> On Thu, 7 Sep 2017 13:51:11 +0800
> Sepherosa Ziehau wrote:
>
>> Weird, your traffic pattern does not even belong to anything heavy.
>>
at 1:07 PM, Paul Koch wrote:
> On Thu, 7 Sep 2017 10:22:40 +0800
> Sepherosa Ziehau wrote:
>
>> Is it possible to tell me your workload? e.g. TX heavy or RX heavy.
>> Enabled TSO or not. Details like how the send syscalls are issue will
>> be interesting. And your W
Ignore ths hn_dec_txdesc.diff, please try this done; should be more effective:
https://people.freebsd.org/~sephe/hn_inc_txbr.diff
On Thu, Sep 7, 2017 at 10:22 AM, Sepherosa Ziehau wrote:
> Is it possible to tell me your workload? e.g. TX heavy or RX heavy.
> Enabled TSO or not. Detail
Is it possible to tell me your workload? e.g. TX heavy or RX heavy.
Enabled TSO or not. Details like how the send syscalls are issue will
be interesting. And your Windows version, include the patch level,
etc.
Please try the following patch:
https://people.freebsd.org/~sephe/hn_dec_txdesc.diff
