Re: RELENG_4 -> 5 -> 6: significant performance regression

2006-04-30 Thread Chris
On 28/04/06, Kris Kennaway <[EMAIL PROTECTED]> wrote: On Fri, Apr 28, 2006 at 03:31:17PM +0300, Dmitry Pryanishnikov wrote: > > Hello! > > On Thu, 27 Apr 2006, Kris Kennaway wrote: > > Thanks for your suggestions, they've made a difference (though not as big > as one could hope). > > >On Thu, Ap

Re: RELENG_4 -> 5 -> 6: significant performance regression

2006-04-30 Thread Peter Jeremy
On Sun, 2006-Apr-30 10:05:40 +0100, Chris wrote: >Does 'makeoptions DEBUG=-g' add any kind of performance hit or >overhead as I noticed it wasnt default in 5.4 but is in 6.0. No. It just means that a debug kernel is built in addition to the normal kernel. The major benefit is that if you do

Re: RELENG_4 -> 5 -> 6: significant performance regression

2006-04-30 Thread Dominic Marks
Peter Jeremy wrote: On Sun, 2006-Apr-30 10:05:40 +0100, Chris wrote: Does 'makeoptions DEBUG=-g' add any kind of performance hit or overhead as I noticed it wasnt default in 5.4 but is in 6.0. No. It just means that a debug kernel is built in addition to the normal kernel. The major bene

Re: fsck_ufs locked in snaplk

2006-04-30 Thread Dmitry Morozovsky
ortant. DM> DM> Well, common usage pattern does not lead to lock today. I made some DM> snapshots on quota'ed file system and delete them successfully. I finally can reproduce this: large rsync with mksnap_ffs in second or third run both locked in snaplk state. Debugging info ava

Re: RELENG_4 -> 5 -> 6: significant performance regression

2006-04-30 Thread Dominic Marks
Dominic Marks wrote: Peter Jeremy wrote: On Sun, 2006-Apr-30 10:05:40 +0100, Chris wrote: Does 'makeoptions DEBUG=-g' add any kind of performance hit or overhead as I noticed it wasnt default in 5.4 but is in 6.0. No. It just means that a debug kernel is built in addition to the normal k

Re: RELENG_4 -> 5 -> 6: significant performance regression

2006-04-30 Thread Kris Kennaway
On Sun, Apr 30, 2006 at 10:05:40AM +0100, Chris wrote: > On 28/04/06, Kris Kennaway <[EMAIL PROTECTED]> wrote: > >On Fri, Apr 28, 2006 at 03:31:17PM +0300, Dmitry Pryanishnikov wrote: > >> > >> Hello! > >> > >> On Thu, 27 Apr 2006, Kris Kennaway wrote: > >> > >> Thanks for your suggestions, they'v

Re: 6.1 prerelease graid3 livelock?

2006-04-30 Thread Bradley W. Dutton
I can reproduce the panic I experienced before. When in single user mode if I try to mount a raid3 array that isn't complete I get the following error: panic: Lock (sx) GEOM topology locked @ /usr/src/sys/geom/raid3/g_raid3.c:775. The full error and alltrace is here: http://duttonbros.com/freebsd/

Re: 6.1 prerelease graid3 livelock?

2006-04-30 Thread Pawel Jakub Dawidek
On Sun, Apr 30, 2006 at 02:59:39PM -0700, Bradley W. Dutton wrote: +> I can reproduce the panic I experienced before. When in single user mode +> if I try to mount a raid3 array that isn't complete I get the following +> error: +> panic: Lock (sx) GEOM topology locked @ +> /usr/src/sys/geom/raid3/g

Question about Item -- Respond Now

2006-04-30 Thread eBay Member
Your registered name is included to show this message originated from eBay. [1]Learn more. [hdrLeft_13x39.gif] Question about Item -- Respond Now eBay [s.gif] eBay sent this message on behalf of an eBay member via My Messages. Responses sent using email will go to the eBay member