On 08/05/2014 17:09, Ed Maste wrote:
On 8 May 2014 04:16, David Demelier wrote:
Hi there,
I'm currently trying vt(9) on a CURRENT kernel (only the kernel not the
base). I have very small bugs, not really serious. I'm currently using the
radeon KMS driver.
* When I switch from a tty to X I can
Hi,
On Fri, May 9, 2014 at 2:54 AM, Warner Losh wrote:
>
> On May 8, 2014, at 3:26 PM, Guy Yur wrote:
>
>> Hi,
>>
>> After the bsd.opts.mk / src.opts.mk split
>> WITHOUT_NIS in src.conf doesn't work.
>
> It should still work… At least that’s the intention...
>
>> src.conf is included in src.opts
> On Wed, 2014-05-07 at 08:39 -0400, Bruno Lauzé wrote:
>> One thing I feel FreeBSD always ignored is instrumentation frameworks.
>> I am talking about wbem, cim model and implementation like OpenPegasus. Why
>> is that?
>> I ported OpenPegasus to work in FreeBSD with few patches.
>> However, of c
On Thu, 2014-05-08 at 16:46 +0400, Alexander V. Chernikov wrote:
> On 07.05.2014 23:24, Sean Bruno wrote:
> > While screwing around with comcast, I can trivially get this panic out
> > of my desktop machine, and am very confused. It seems to happen on link
> > change up/down events. I'm running 1
On Thursday, May 08, 2014 11:43:39 pm Adrian Chadd wrote:
> Hi,
>
> I'd like to revisit this now.
>
> I'd like to commit this stuff as-is and then take some time to revisit
> the catch-all softclock from cpu0 swi. It's more complicated than it
> needs to be as it just assumes timeout_cpu == cpuid
On 9 May 2014 10:49, John Baldwin wrote:
> On Thursday, May 08, 2014 11:43:39 pm Adrian Chadd wrote:
>> Hi,
>>
>> I'd like to revisit this now.
>>
>> I'd like to commit this stuff as-is and then take some time to revisit
>> the catch-all softclock from cpu0 swi. It's more complicated than it
>> ne
How about i instead do the comprimise:
* i'll pin all other swi's
* default swi isn't pinned by default, but one can flip on a sysctl at
boot time to pin it
How's that sound?
And also please a sysctl that disables any swi pinning.
It is sometimes useful to change the default cpuset, for ins
since they are in
> the default set.
>
> (Note that some network drivers are also culprits here, though disabling
> MSI-x in them is a workaround).
Yup. I've just done that.
http://people.freebsd.org/~adrian/norse/20140509-swi-pin-1.diff
Which workloads are you thinking about? Mayb
On Friday, May 09, 2014 3:50:28 pm Peter Grehan wrote:
> > How about i instead do the comprimise:
> >
> > * i'll pin all other swi's
> > * default swi isn't pinned by default, but one can flip on a sysctl at
> > boot time to pin it
> >
> > How's that sound?
>
> And also please a sysctl that disa
Yup. I've just done that.
http://people.freebsd.org/~adrian/norse/20140509-swi-pin-1.diff
Thanks, that'll work.
Which workloads are you thinking about? Maybe we could introduce some
higher level description of which CPU(s) at boot time to do "freebsd
stuff" on, and the
On 9 May 2014 16:49, Peter Grehan wrote:
>> Yup. I've just done that.
>>
>> http://people.freebsd.org/~adrian/norse/20140509-swi-pin-1.diff
>
>
> Thanks, that'll work.
>
>
>> Which workloads are you thinking about? Maybe we could introduce some
&g
ok, I've committed it but I've left the default at "don't pin."
That way the existing behaviour hasn't changed and it's easy to flip
on to play with.
Thanks for the feedback John / Peter!
-a
___
freebsd-current@freebsd.org mailing list
http://lists.fr
12 matches
Mail list logo
