Terry Lambert wrote:
> Peter Wemm wrote:
> > Terry Lambert wrote:
> > > Mike Silbersack wrote:
> > > > 1. Have the ata driver leave the write cache setting
> > > > alone by default, providing a sysctl which can cause
> > > > disabled or enabled if requested. When the default is
> > > > allowed,
Mike Silbersack wrote:
>
> On Fri, 1 Jun 2001, Terry Lambert wrote:
>
> > First of all, they do not "run circles" around FreeBSD;
> > they kill the virgin reliability on the alter of the
> > bloody god Benchmark.
>
> Ok, Terry, you've made it clear that you hate IDE, you
> hate linux, and you p
On Fri, 1 Jun 2001, Terry Lambert wrote:
> First of all, they do not "run circles" around FreeBSD;
> they kill the virgin reliability on the alter of the
> bloody god Benchmark.
Ok, Terry, you've made it clear that you hate IDE, you hate linux, and you
pretty much hate everything other than sof
Peter Wemm wrote:
> Terry Lambert wrote:
> > Mike Silbersack wrote:
> > > 1. Have the ata driver leave the write cache setting
> > > alone by default, providing a sysctl which can cause
> > > disabled or enabled if requested. When the default is
> > > allowed, put something in dmesg which says "
Mike Silbersack wrote:
> > As a friend of mine says "I can make it go as fast as you
> > want, if it doesn't have to work"...
>
> You entirely missed my point. Yes, we could leave it at 0.
> But if so, we should tell people so that they can make an
> informed choice. If we don't make the choice
Kris Kennaway wrote:
> > > 1. Have the ata driver leave the write cache setting
> > > alone by default, providing a sysctl which can cause
> > > disabled or enabled if requested. When the default is
> > > allowed, put something in dmesg which says "Note: Write
> > > caching may be enabled. See
Terry Lambert wrote:
> Mike Silbersack wrote:
> > 1. Have the ata driver leave the write cache setting
> > alone by default, providing a sysctl which can cause
> > disabled or enabled if requested. When the default is
> > allowed, put something in dmesg which says "Note: Write
> > caching may be
On Wed, 30 May 2001, Terry Lambert wrote:
> Mike Silbersack wrote:
> > 1. Have the ata driver leave the write cache setting
> > alone by default, providing a sysctl which can cause
> > disabled or enabled if requested. When the default is
> > allowed, put something in dmesg which says "Note: W
On Wed, May 30, 2001 at 03:59:59AM -0700, Terry Lambert wrote:
> > 1. Have the ata driver leave the write cache setting
> > alone by default, providing a sysctl which can cause
> > disabled or enabled if requested. When the default is
> > allowed, put something in dmesg which says "Note: Write
Mike Silbersack wrote:
> As to technical arguments for enabling write caching under
> uncertain power conditions, I can't come up with any.
> (Until the BIO_ORDERED work is done; is anyone actually
> working on it?)
Apparently IBM has finally released an IDE drive that can
do tagged command queue
Ed Hudson wrote:
>
> the cost of soft updates, and the cost of hw.ata.wc=0
>
> enclosed is a .jpeg of an xgraph of the following interactive test:
[ ... ]
> hw.ata.wc=0, soft-updates enables.
> hw.ata.wc=0, soft-updates disabled.
> hw.ata.wc=1, soft-updates disabled.
>
On Mon, 28 May 2001, Daniel C. Sobral wrote:
> Rik van Riel wrote:
> > On Fri, 25 May 2001, Terry Lambert wrote:
> >
> > > So add an option to sysinstall called:
> > >
> > > "Fast and at least as reliable as Linux"
> >
> > I doubt FreeBSD would need to enable write caching in order
> > to
Rik van Riel wrote:
>
> On Fri, 25 May 2001, Terry Lambert wrote:
>
> > So add an option to sysinstall called:
> >
> > "Fast and at least as reliable as Linux"
>
> I doubt FreeBSD would need to enable write caching in order
> to be as fast as Linux (which doesn't have write caching
> enab
On Fri, 25 May 2001, Terry Lambert wrote:
> So add an option to sysinstall called:
>
> "Fast and at least as reliable as Linux"
>
> and let them find out for themselves that that means that it's
> really dangerous, and that after a crash for whatever reason (e.g.
> your panic crash, or a p
> I doubt FreeBSD would need to enable write caching in order
> to be as fast as Linux (which doesn't have write caching
i spoke too harshly.
what i meant to show is that interactive performance
is compromised under load with soft updates enabled
(although soft upd
On Fri, May 25, 2001 at 11:21:06PM -0700, Ed Hudson wrote:
> enclosed is a .jpeg of an xgraph of the following interactive test:
Are you setup such that you could do the same test on a stock Red Hat
6.2, 7.0, and 7.1 box?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-h
On Fri, 25 May 2001, Terry Lambert wrote:
> So add an option to sysinstall called:
>
> "Fast and at least as reliable as Linux"
I doubt FreeBSD would need to enable write caching in order
to be as fast as Linux (which doesn't have write caching
enabled in any distribution I'm aware of).
the cost of soft updates, and the cost of hw.ata.wc=0
enclosed is a .jpeg of an xgraph of the following interactive test:
a monitor computer, rsh's to a test machine and does a 'date' command,
then waits 5 seconds, and repeats.
on the test machine, an athlon 1.2gig / 266fsb / 512meg/133(266ddr
] That mood is nice in theory, but doesn't seem to fit practice. My boxes
] are on UPSes, and I have trouble remembering the last time the power went
] out. On the other hand, I can clearly remember the last panic
] on my -current box which required a manual fsck to repair (yesterday).
] And yes
Mike Silbersack wrote:
>
> On Thu, 24 May 2001, Doug Barton wrote:
>
> > The current mood (which I agree with) is to make softupdates the default
> > after installation. The problem with the combo of write caching and
> > softupdates is that if the power actually goes off the meta-data wri
Hi,
On Fri, May 25, 2001 at 12:10:49PM -0500, Mike Silbersack wrote:
>
> On Thu, 24 May 2001, Doug Barton wrote:
>
> And stuck in the middle is a growing number of people who are seeing a
> noticeable slowdown with 4.3, and will start telling their friends that
> FreeBSD is slow.
>
> Mike "Sil
On Thu, 24 May 2001, Doug Barton wrote:
> The current mood (which I agree with) is to make softupdates the default
> after installation. The problem with the combo of write caching and
> softupdates is that if the power actually goes off the meta-data writes
> that softupdates postpones an
On Thu, May 24, 2001 at 11:19:44PM -0700, Doug Barton wrote:
> The current mood (which I agree with) is to make softupdates the default
> after installation. The problem with the combo of write caching and
> softupdates is that if the power actually goes off the meta-data writes
> that soft
Ed Hudson wrote:
>
> fyi, here's another hw.ata.wc=1 vs hw.ata.wc=0 comparison:
>
> 4.3-RELEASE install, ASUS A7V, 800mhz, hw.ata.wc=0, express install +all,
> 60gig wd-600b udma100 drive, partitioned as:
>
> /8192m
> swap 1024m
>
fyi, here's another hw.ata.wc=1 vs hw.ata.wc=0 comparison:
4.3-RELEASE install, ASUS A7V, 800mhz, hw.ata.wc=0, express install +all,
60gig wd-600b udma100 drive, partitioned as:
/8192m
swap 1024m
/xtra 48023m
install
On Thu, May 24, 2001 at 07:30:28PM +0200, Erik Trulsson wrote:
> On Thu, May 24, 2001 at 10:18:13AM -0700, Ted Faber wrote:
> > read-only, a one-liner in the ata man page (that I'm happy to write)
> > would be a good thing.
>
> The relevant one-liner from the ata(4) man page is:
>The follo
On Thu, May 24, 2001 at 10:18:13AM -0700, Ted Faber wrote:
> On Thu, May 24, 2001 at 12:48:02AM -0500, Mike Silbersack wrote:
> > Write caching is now off by default. man ata to see how to turn it back
> > on.
>
> U. I setting hw.ata.wc=1 and got:
>
> ted:~$ sudo sysctl -w hw.ata.wc=1
> sy
On Thu, May 24, 2001 at 12:48:02AM -0500, Mike Silbersack wrote:
> Write caching is now off by default. man ata to see how to turn it back
> on.
U. I setting hw.ata.wc=1 and got:
ted:~$ sudo sysctl -w hw.ata.wc=1
sysctl: oid 'hw.ata.wc' is read only
I'm assuming that this is because my co
Thus spake Ed Hudson ([EMAIL PROTECTED]):
> for my money, hw.ata.wc=1 soft updates OFF is a better performing
> choice than hw.ata.wc=0 and soft updates ON.
> (soft updates are great, but i really dislike the performance
> stalls that it (or async mode) engenders with big
Mike Silbersack <[EMAIL PROTECTED]> writes:
> Write caching is now off by default. man ata to see how to turn it back
> on.
Mr. Silbersack, thank you very much. you've restored my
systems to their pre-4.3 stunningly fast behavior.
to the hackers group, i apologize for p
On Wed, 23 May 2001, Ed Hudson wrote:
>
> howdy.
>
> maybe this has been discussed in 'hackers' or elsewhere,
> before - i can't find a reference via the search interface.
>
> i'm a long time freebsd user, and i've been struck by how much my
> systems (3 of them) have slowed dow
howdy.
maybe this has been discussed in 'hackers' or elsewhere,
before - i can't find a reference via the search interface.
i'm a long time freebsd user, and i've been struck by how much my
systems (3 of them) have slowed down in its disk performance with
4.3-RELEASE, relat
32 matches
Mail list logo
