On Tue, Aug 26, 2014 at 03:05:41PM -0700, Adrian Chadd wrote:
> This to me reads like "we need to fix pmc's locking so it's not so
> terrible on multi-multi-core-machines." :)
I am may be wrong, but I don't see in pmc interrupt path.
May be this is need fix too?
> On 26 August 2014 11:54, Slawa
This to me reads like "we need to fix pmc's locking so it's not so
terrible on multi-multi-core-machines." :)
-a
On 26 August 2014 11:54, Slawa Olhovchenkov wrote:
> On Tue, May 20, 2014 at 09:04:25AM -0700, Adrian Chadd wrote:
>
>> On 20 May 2014 08:41, Slawa Olhovchenkov wrote:
>>
>> >> (B
On Tue, Aug 26, 2014 at 10:35:21PM +0300, Alexander Motin wrote:
> On 26.08.2014 21:54, Slawa Olhovchenkov wrote:
> > On Tue, May 20, 2014 at 09:04:25AM -0700, Adrian Chadd wrote:
> >
> >> On 20 May 2014 08:41, Slawa Olhovchenkov wrote:
> >>
> (But if you try it on 10.0 and it changes thing
On 26.08.2014 21:54, Slawa Olhovchenkov wrote:
> On Tue, May 20, 2014 at 09:04:25AM -0700, Adrian Chadd wrote:
>
>> On 20 May 2014 08:41, Slawa Olhovchenkov wrote:
>>
(But if you try it on 10.0 and it changes things, by all means let me
know.)
>>>
>>> I am try on 10.0, but not sure abo
On Tue, May 20, 2014 at 09:04:25AM -0700, Adrian Chadd wrote:
> On 20 May 2014 08:41, Slawa Olhovchenkov wrote:
>
> >> (But if you try it on 10.0 and it changes things, by all means let me
> >> know.)
> >
> > I am try on 10.0, but not sure about significant improvement (may be
> > 10%).
> >
> >
On 20 May 2014, at 16:26 , Slawa Olhovchenkov wrote:
> On Tue, May 20, 2014 at 09:04:25AM -0700, Adrian Chadd wrote:
>
>> On 20 May 2014 08:41, Slawa Olhovchenkov wrote:
>>
(But if you try it on 10.0 and it changes things, by all means let me
know.)
>>>
>>> I am try on 10.0, but n
On Tue, May 20, 2014 at 09:04:25AM -0700, Adrian Chadd wrote:
> On 20 May 2014 08:41, Slawa Olhovchenkov wrote:
>
> >> (But if you try it on 10.0 and it changes things, by all means let me
> >> know.)
> >
> > I am try on 10.0, but not sure about significant improvement (may be
> > 10%).
> >
> >
On 20 May 2014 08:41, Slawa Olhovchenkov wrote:
>> (But if you try it on 10.0 and it changes things, by all means let me know.)
>
> I am try on 10.0, but not sure about significant improvement (may be
> 10%).
>
> For current CPU (E5-2650 v2 @ 2.60GHz) hwpmc don't working (1. after
> collect some
On Sun, May 11, 2014 at 08:32:34AM -0700, Adrian Chadd wrote:
> On 11 May 2014 01:31, Slawa Olhovchenkov wrote:
> > On Sat, May 10, 2014 at 12:53:37AM +, Adrian Chadd wrote:
> >
> >> Author: adrian
> >> Date: Sat May 10 00:53:36 2014
> >> New Revision: 265792
> >> URL: http://svnweb.freebsd.o
On 11 May 2014 01:31, Slawa Olhovchenkov wrote:
> On Sat, May 10, 2014 at 12:53:37AM +, Adrian Chadd wrote:
>
>> Author: adrian
>> Date: Sat May 10 00:53:36 2014
>> New Revision: 265792
>> URL: http://svnweb.freebsd.org/changeset/base/265792
>>
>> Log:
>> Add in support to optionally pin the
On Sat, May 10, 2014 at 12:53:37AM +, Adrian Chadd wrote:
> Author: adrian
> Date: Sat May 10 00:53:36 2014
> New Revision: 265792
> URL: http://svnweb.freebsd.org/changeset/base/265792
>
> Log:
> Add in support to optionally pin the swi threads.
>
> Under enough load, the swi's can ac
Author: adrian
Date: Sat May 10 00:53:36 2014
New Revision: 265792
URL: http://svnweb.freebsd.org/changeset/base/265792
Log:
Add in support to optionally pin the swi threads.
Under enough load, the swi's can actually be preempted and migrated
to other currently free cores. When doing RSS
12 matches
Mail list logo