The iterator changes I committed are a
> more generic version of a patch people were applying on top of -10 and
> -head for at least what, three years now? Maybe more if -9 also just
> did round-robin and not first-touch?
8 and 9 did first-touch. Only 10 did
On Wednesday, August 13, 2014 1:00:22 pm Alan Cox wrote:
> On Tue, Aug 12, 2014 at 1:09 PM, John Baldwin wrote:
>
> > On Wednesday, July 16, 2014 1:52:45 pm Adrian Chadd wrote:
> > > Hi!
> > >
> > >
> > > On 16 July 2014 06:29, Konstantin Belous
On Tuesday, August 12, 2014 5:36:26 pm Adrian Chadd wrote:
> On 12 August 2014 11:09, John Baldwin wrote:
> > On Wednesday, July 16, 2014 1:52:45 pm Adrian Chadd wrote:
> >> Hi!
> >>
> >>
> >> On 16 July 2014 06:29, Konstantin Belousov wrote:
&g
ied. (I have a local hack that adds a new malloc option to explicitly
memset() new pages allocated via mmap() that gives the same benefit without
the junking overheadon each malloc() / free(), but it does increase physical
RAM usage.)
--
John Baldwin
___
freebsd-performance@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-performance
To unsubscribe, send any mail to "freebsd-performance-unsubscr...@freebsd.org"
kib/pgsql_perf.pdf.
> The uncommitted patches, referenced in the article, are available as
> https://kib.kiev.ua/kib/pig1.patch.txt
> https://kib.kiev.ua/kib/patch-2
Did you run the same benchmark on the same hardware with any other OS's to
co
onf as well. They do not have
to be listed in bsd.own.mk. World builds include /etc/src.conf whereas
every make invocation includes /etc/make.conf via sys.mk. The only reason
to use /etc/src.conf is to have a place to put variables only affect
make buil
eue and each CPU
just grabs the head of the queue when it finishes a timeslice. ULE always
assigns threads to a single CPU (even if they aren't pinned to a single
CPU using cpuset, etc.) and then tries to balance the load across cores
later, but I believe in this case it's rebalanc
e (I know what
> determines the quality of a clock visually from a oscilloscope =])?
I suspect that the quality of the HPET driver is lower simply because no one
had measured it previously and HPET is newer and less "proven".
--
John Baldwin
On Tuesday 18 March 2008 09:04:05 am Robert Watson wrote:
> On Tue, 18 Mar 2008, John Baldwin wrote:
> >> '+' is used in a swi name to indicate that the names of the interrupts
> >> to put in the thread name are too long, and the code looks like it was
> >&
this. It
> would be nice if we had a way to export information on all the interrupt
> event sources, including soft ones, and their mappings to ithreads,
> including swis, using sysctl. Or maybe we do already and he'll point us at
> it. :-)
We don't and that is what we need
10 matches
Mail list logo
