Hi Robert,
the benchmark you cited is for uniprocessor systems only.
It says nothing about multiprocessor performance, which is what FreeBSD
is aiming for.
It's comparing apples with oranges.
Cheers,
Gerald
Robert Ryan wrote:
Fellow FreeBSD developers,
I hate to say I told you but it was inevitab
--- Gerald Heinig <[EMAIL PROTECTED]> wrote:
> Hi Robert,
>
> the benchmark you cited is for uniprocessor systems
> only.
> It says nothing about multiprocessor performance,
> which is what FreeBSD
> is aiming for.
Doesn't the (ULE) scheduler have a switch to ensure
that performance is optimal
On Fri, Jan 07, 2005 at 01:10:04AM -0800, Kamal R. Prasad wrote:
>
> > Hi Robert,
> >
> > the benchmark you cited is for uniprocessor systems
> > only.
> > It says nothing about multiprocessor performance,
> > which is what FreeBSD
> > is aiming for.
> Doesn't the (ULE) scheduler have a switch t
Hi Kamal,
I don't know about any switches for ULE. My point is that it's not
particularly meaningful to compare a system that's built for SMP to one
that isn't. There have been a number of tests (sorry, don't have time to
dig them all out) of systems with MP locks against systems without on a
u
Am Freitag, 7. Januar 2005 09:58 schrieb Gerald Heinig:
> Hi Robert,
>
> the benchmark you cited is for uniprocessor systems only.
> It says nothing about multiprocessor performance, which is what FreeBSD
> is aiming for.
> It's comparing apples with oranges.
No, many users, me included, only run
On Fri, Jan 07, 2005 at 09:21:10AM +, Ceri Davies wrote:
> I don't really think that this benchmark is bad news for either OS. My
> only real concern are the process creation/termination results on FreeBSD.
I guess that this might worth investigating:
http://people.freebsd.org/~das/p
On Fri, 7 Jan 2005 20:40, Xin LI wrote:
> On Fri, Jan 07, 2005 at 09:21:10AM +, Ceri Davies wrote:
> > I don't really think that this benchmark is bad news for either OS. My
> > only real concern are the process creation/termination results on
> > FreeBSD.
>
> I guess that this might worth inv
The upgrade to 5-CURRENT did it.
sk0 now works fine !
On 5 Jan 2005 at 11:14, "Bjoern A. Zeeb" Doing it right now!!
>
> Thanks,
>
> --
>//| //||
> // | // ||
> -//--//---|| ARIO LOBO
> // //||
> -
> [EMAIL PROTECTED]
> http://www.ipad.com.br
>
> On
Hello;
On all installations of FreeBSD I´ve ever done in the past,
netstat -an
displays LISTENing servers and any tcp connection in any state.
On the 5.3 I have installed here ( updated to RELENG_5_3 + build/installworld
), this command only
shows only this;
--
[EMAIL PROTECTED]
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
[EMAIL PROTECTED] wrote:
> On all installations of FreeBSD I?ve ever done in the past,
>
> netstat -an
>
> displays LISTENing servers and any tcp connection in any state.
>
> On the 5.3 I have installed here ( updated to RELENG_5_3 + build/installworld
> ), this command only
> shows only this;
On Thu, Jan 06, 2005 at 06:21:54PM -0800, Pascal Hofstee wrote:
>
> I guess to sum it all up it all boils down to the following question.
>
> Is it intended that kvm_getargv() apparently has a conditional under
> which it depends on the existince of a working /proc .. even though
> the manpage st
Hello, I've noticed a discrepancy between the ALTQ manpage and the
release notes (both in 5.3):
altq(4) says:
SUPPORTED DEVICES
The driver modifications described in altq(9) and required to use
a certain network card with ALTQ have been applied to the
following hardware drivers an(4
Tried that before posting. this is what I get
Active Internet connections (including servers)
Proto Recv-Q Send-Q Local Address Foreign Address(state)
udp4 0 0 *.514 *.*
On 7 Jan 2005 at 10:56, Jose Hidalgo Herrera wrote:
>
> What about
> netstat
That´s it !!
I´ve been having trouble with a sk0 gigabit ethernet and updated the kernel to
5_CURRENT
to update it with jumbo frame support, But userland was updated to RELENG_5_3
only !!
I knew about that but the system ran smooth after compiling the new kernel,
I did not think it would make a
Sorry for wasting everyones bandwidth and time .. thanks to Dominic
Marks I have re-read my own question and actually *read* the altq(9)
manpage in addition to the altq(4) manpage... I make the conclusion
that if the IFQ_* macros are used in the driver source, the driver is
ALTQified.
I also draw
What about
netstat -anf inet
El vie, 07-01-2005 a las 09:06 -0300, [EMAIL PROTECTED] escribió:
> Hello;
>
> On all installations of FreeBSD I´ve ever done in the past,
>
> netstat -an
>
> displays LISTENing servers and any tcp connection in any state.
>
> On the 5.3 I have installed h
Hello,
We recently did work with the Cqual type inference tool to identify
potential user/kernel pointer bugs in FreeBSD 5.3. Our paper is
available here: http://www.node99.org/projects/bsduk/
We identified 5 potential bugs which we are looking to confirm with the
community. Page 10 contains
Sean Whalen wrote:
We recently did work with the Cqual type inference tool to identify
potential user/kernel pointer bugs in FreeBSD 5.3. Our paper is
available here: http://www.node99.org/projects/bsduk/
We identified 5 potential bugs which we are looking to confirm with the
community. Page
I have separately posted this to freebsd-security as it seemed relevant to both
lists.
The blowfish crypt(3) mechanism supports the use of a "cost value" for password
encryption. The cost value is encoded into the encrypted password that is
stored in master.passwd. On OpenBSD, this cost value
20 matches
Mail list logo