On Sat, 6 Mar 2010, Kevin Day wrote:
> > ISTR FreeBSD defaults to a very conservative setting here so you
> > may have to set it manually.
>
> Yeah, sorry for not mentioning that I had tried this and didn't see
> any change, so I thought I was on the wrong track.
OK.
> Is the note about adding hi
On Mar 6, 2010, at 12:05 AM, Daniel O'Connor wrote:
> On Sat, 6 Mar 2010, Kevin Day wrote:
>> So, it seems that the VMware hypervisor is deactivating cores on the
>> CPU when idle, but FreeBSD itself isn't. Is anyone working on giving
>> FreeBSD's idle loop/scheduler the ability to go into deeper
On Sat, 6 Mar 2010, Kevin Day wrote:
> So, it seems that the VMware hypervisor is deactivating cores on the
> CPU when idle, but FreeBSD itself isn't. Is anyone working on giving
> FreeBSD's idle loop/scheduler the ability to go into deeper sleep
> states? It seems this would have more than just a
Recently I bumped into something very weird. In some CPU heavy workloads,
FreeBSD ran faster inside VMware's ESX hypervisor than it did running natively
on bare metal. Simple pure CPU applications (such as "openssl speed") would run
10-30% faster on VMware. This seemed very counterintuitive, un
Just wanted to followup with a summary before all vestiges of what I
learned evaporate from my memory. My apologies for the lateness.
1. Existing FreeBSD ata-disk code does not explicitly park the hard
drive heads on shutdown. So the power loss causes an emergency park,
which sounds bad and
'Lo.
As a test, I've now stripped nullfs out of the picture entirely. The
exact same problem still occurs:
Creating package /pkg/All/libgpg-error-1.7.tbz
Registering depends: gettext-0.17_1 libiconv-1.13.1_1.
Creating bzip'd tar ball in '/pkg/All/libgpg-error-1.7.tbz'
rmdir: /work/ports/security/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2010/03/05 11:59, Alexander Best wrote:
> Xin LI schrieb am 2010-03-05:
> On 2010/03/05 11:26, Alexander Best wrote:
hi there. does this look right?
>
> Not to me, the value is not to be used this way and the comments
> above
> the code explai
Xin LI schrieb am 2010-03-05:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
> On 2010/03/05 11:26, Alexander Best wrote:
> > hi there. does this look right?
> Not to me, the value is not to be used this way and the comments
> above
> the code explained the same thing.
> I think we should use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2010/03/05 11:26, Alexander Best wrote:
> hi there. does this look right?
Not to me, the value is not to be used this way and the comments above
the code explained the same thing.
I think we should use cputick2usec but it's not available to userla
hi there. does this look right?
cheers.
alex
Index: lib/libkvm/kvm_proc.c
===
--- lib/libkvm/kvm_proc.c (revision 204763)
+++ lib/libkvm/kvm_proc.c (working copy)
@@ -371,7 +371,7 @@
* to convert cputicks
ion in multiple
> places:
>
> # Mount one dataset wherever you need it.
> zfs set mountpoint=/path/to/wherever pool/packages
>
> # Create a snapshot and clone it for further mountpoints.
> zfs snapshot pool/packa...@20100305
> zfs clone pool/packa...@20100305 pool/packages2
>
On Friday 05 March 2010 07:01:00 John Baldwin wrote:
> On Thursday 04 March 2010 4:33:29 pm David Wolfskill wrote:
> > For reasons that may well be idiosyncratic, I like to set up FreeBSD
> > machines to have at least 2 bootable slices -- e.g., one can act as a
> > fallback if an attempted software
On Fri, Mar 5, 2010 at 1:19 PM, Robert Watson wrote:
>
> On Thu, 4 Mar 2010, sean connolly wrote:
>
>> Automatic reporting would end up being a mess given that panics can be
>> caused by hardware problems. Having an autoreport check if memtest was run
>> before it reports, or having it only run wi
Bruce Cran schrieb am 2010-03-05:
> On Friday 05 March 2010 05:28:39 Alexander Best wrote:
> > any suggestions on how to successfully build world with debugging
> > symbols
> > are welcome.
> Use DEBUG_FLAGS instead:
> DEBUG_FLAGS=-g
ahh. thanks for the hint. with DEBUG_FLAGS i was able to bui
lection in multiple
places:
# Mount one dataset wherever you need it.
zfs set mountpoint=/path/to/wherever pool/packages
# Create a snapshot and clone it for further mountpoints.
zfs snapshot pool/packa...@20100305
zfs clone pool/packa...@20100305 pool/packages2
zfs set mountpoint=/path/to/othe
On Thursday 04 March 2010 4:33:29 pm David Wolfskill wrote:
> For reasons that may well be idiosyncratic, I like to set up FreeBSD
> machines to have at least 2 bootable slices -- e.g., one can act as a
> fallback if an attempted software upgrade proves to have been ill-timed.
>
> In the past, I'v
On Thursday 04 March 2010 8:50:56 am sean connolly wrote:
> Hi Dan,
>
> Automatic reporting would end up being a mess given that panics can be
caused by hardware problems. Having an autoreport check if memtest was run
before it reports, or having it only run with -CURRENTmight be useful.
That'
xorquew...@googlemail.com writes:
> Is there any resolution for this problem?
I told you, zfs set mountpoint and ditch nullfs.
DES
--
Dag-Erling Smørgrav - d...@des.no
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listin
On Thu, 4 Mar 2010, sean connolly wrote:
Automatic reporting would end up being a mess given that panics can be
caused by hardware problems. Having an autoreport check if memtest was run
before it reports, or having it only run with -CURRENTmight be useful.
Hi Sean, Dan, et al:
I'm not sure
On Friday 05 March 2010 05:28:39 Alexander Best wrote:
> any suggestions on how to successfully build world with debugging symbols
> are welcome.
Use DEBUG_FLAGS instead:
DEBUG_FLAGS=-g
The build system knows not to strip the binaries when that's defined, too.
--
Bruce Cran
_
20 matches
Mail list logo
