On Mon, Sep 24, 2001 at 08:56:08AM +0200, Cyrille Lefevre wrote:
> what kind of issues ? I'm using both XFree86-4 and ports in package form
> (pre-compiled stuffs) w/o any problems.
Please RTF /usr/ports/Mk/bsd.port.mk and look at what "XFREE86_VERSION"
does.
--
-- David ([EMAIL PROTECTED])
T
David O'Brien wrote:
> On Sun, Sep 23, 2001 at 04:05:27PM +0200, Cyrille Lefevre wrote:
> > David O'Brien wrote:
> > > On Mon, Sep 17, 2001 at 05:42:23PM -0700, Jordan Hubbard wrote:
> > > > We're still waiting for 4.0's "support footprint" to widen
> > > > a bit more before subjecting people to i
In message <[EMAIL PROTECTED]>, Julian Elischer writes:
>Matt Dillon wrote:
>>
>> :Block input operations is the one notable exception and it tells a
>> :very interesting story: Matts patch results in a 4% increase, but
>> :combined with vmdirioenable it results in a 21.5% decrease.
>> :
>> :That
Ok, here are the first set of results. I am going to rerun the entire
suite of tests again with the machines limited to 128M of ram to see
what happens then.
BTW, these are really nice machines! I highly recommend DELL2550's.
The results w/ 512M are basically that it doesn'
I got the cache_leaf_test() return values backwards. But that's ok,
because my cache_leaf_test() if() statement is also backwards :-). I'll
turn them around in a later patch set.
-Matt
To Unsubscribe: send mail to [EMAIL PROTECTED]
wi
:Notice that both the user and system times increased..
:if there had been another parallel task, the overall system throughout may have
:decreased..
:
:I'm not saying this is wrong, just that we should look at other workloads too.
:no point in optimising the system for compiling itself.. that's
fdirs())
References: <1620.1001272770@critter>
:
:Here is the latest patch for -stable. vmiodirenable is turned on by
:default, the cache purge code is enabled based on vmiodirenable, and
:I added a new sysctl called nameileafonly which defaults to ON (1).
:
:nameileafonly vmi
Matt Dillon wrote:
>
> :Block input operations is the one notable exception and it tells a
> :very interesting story: Matts patch results in a 4% increase, but
> :combined with vmdirioenable it results in a 21.5% decrease.
> :
> :That's pretty darn significant: one out of every five I/O have
> :b
Here is the latest patch for -current. vmiodirenable is turned on by
default, the cache purge code is enabled based on vmiodirenable, and
I added a new sysctl called nameileafonly which defaults to ON (1).
The old cache_purgeleafdirs() stuff is #if 0'd out.
nameileafonly vmio
Here is the latest patch for -stable. vmiodirenable is turned on by
default, the cache purge code is enabled based on vmiodirenable, and
I added a new sysctl called nameileafonly which defaults to ON (1).
nameileafonly vmiodirenable action
1 1 (DEFAULT
It seems Dave Hayes wrote:
>
> ad1: READ command timeout tag=0 serv=0 - resetting
> ata0: resetting devices .. done
> ad1a: hard error reading fsbn 5068879 (ad1 bn 5068879; cn 315 tn 133 sn
> 25)ad1a: hard error reading fsbn 5068879 (ad1 bn 5068879; cn 315 tn 133 sn 25)
> status=59 error=40
>
:Has the problem of small-memory machines (< 64M IIRC) solved now? As I
:understand it vmiodirenable is counter-productive for these boxes.
:Maybe one could decide on-boot whether the amount of mem is enough to
:make it useful?
:
:Just a thought of course.
:
:| / o / /_ _emai
:Block input operations is the one notable exception and it tells a
:very interesting story: Matts patch results in a 4% increase, but
:combined with vmdirioenable it results in a 21.5% decrease.
:
:That's pretty darn significant: one out of every five I/O have
:been saved.
:
:The reason it has n
I ran one of my trivial benchmarks here: "make -j 12 buildworld"
on a dual 866MHz P3 with 640M RAM.
Most of the stuff reported by "/usr/bin/time -l" here is useless:
almost all the numbers are all inside the standard deviation I have
recorded for them on this box.
Block input operations is the
On Sun, Sep 23, 2001 at 04:05:27PM +0200, Cyrille Lefevre wrote:
> David O'Brien wrote:
> > On Mon, Sep 17, 2001 at 05:42:23PM -0700, Jordan Hubbard wrote:
> > > We're still waiting for 4.0's "support footprint" to widen
> > > a bit more before subjecting people to it by default. Hopefully
> > >
We've been attempting to set up a vinum raid box with a bunch of IDE
drives. Each drive is partitioned with a vinum partition on A, such
that the entire drive is on partition a. Initial partitioning is done
with /stand/sysinstall so it "fixes" my geometry, this has always
worked in the past.
I ha
Hello,
After compiling a new kernel, installing it, when my laptop
tries to mount its drive, it panics with this message:
panic: lock (sleep mutex) vnode interlock not locked @
../../../kern/vfs_default.c:460
which is:
if (ap->a_flags & LK_INTERLOCK)
mtx_unlock(&ap->a_vp->v_int
David O'Brien wrote:
> On Mon, Sep 17, 2001 at 05:42:23PM -0700, Jordan Hubbard wrote:
> > We're still waiting for 4.0's "support footprint" to widen
> > a bit more before subjecting people to it by default. Hopefully
> > by 4.5.
>
> Are you really considering using XFree86 4.x in FreeBSD-4.5?
>
In message <[EMAIL PROTECTED]>, Matt Dillon writes:
>Ah yes, vmiodirenable. We should just turn it on by default now. I've
>been waffling too long on that. With it off the buffer cache will
>remember at most vfs.maxmallocspace worth of directory data (read: not
>very much), an
On Sun, Sep 23, 2001 at 03:40:33AM -0700, Matt Dillon wrote:
>
> :>VM Page Cache, and thus not be candidates for reuse anyway. So my patch
> :>has a very similar effect but without the overhead.
> :
> :Back when I rewrote the VFS namecache back in 1997 I added that
> :clause because I sa
:>VM Page Cache, and thus not be candidates for reuse anyway. So my patch
:>has a very similar effect but without the overhead.
:
:Back when I rewrote the VFS namecache back in 1997 I added that
:clause because I saw directories getting nuked in no time because
:there were no pages holdi
In message <[EMAIL PROTECTED]>, Matt Dillon writes:
>My patch doesn't make a distinction but assumes that (A) will tend to
>hold for higher level directories: that is, that higher level directories
>tend to be accessed more often and thus will tend to have pages in the
>VM Page
: Hmmm. This would seem to be a step back to the days when caching was done
:relative to the device as opposed to the file-relative scheme we have now.
:One of the problems with the old scheme as I recall is that some filesystems
:like NFS don't have a 'device' and thus no physical block numbers
:>Well, this has turned into a rather sticky little problem. I've
:>spent all day going through the vnode/name-cache reclaim code, looking
:>both at Seigo's cache_purgeleafdirs() and my own patch.
:
: Can you forward me your patch? I'd like to try it out on some machines in
:the TS
24 matches
Mail list logo
