Re: Unable to get RealTek 8139C+ to work with re(4) under FreeBSD 6.1

2006-08-16 Thread Pyun YongHyeon
On Thu, Aug 17, 2006 at 02:05:48PM +0800, Dinesh Nair wrote: > > > On 08/16/06 20:37 Pyun YongHyeon said the following: > >If the media is set to 'none' you couldn't send anything from re(4) as > >recent changes checks whether the link is present(Receiver should work). > > ifconfig re0 me

Re: Unable to get RealTek 8139C+ to work with re(4) under FreeBSD 6.1

2006-08-16 Thread Dinesh Nair
On 08/16/06 20:37 Pyun YongHyeon said the following: If the media is set to 'none' you couldn't send anything from re(4) as recent changes checks whether the link is present(Receiver should work). ifconfig re0 media 10baset or 100baset always returns error, so there doesn't seem to be anyway

Re: openospfd

2006-08-16 Thread David Gilbert
> "Yann" == Yann Berthier <[EMAIL PROTECTED]> writes: Yann> On Tue, 15 Aug 2006, at 19:59, David Gilbert wrote: >> Is there anyone actively working on openospfd (the port)? Yann>I ended up taking a snapshot of openospf at that time and Yann> removing all route labels reference to compile

Re: Unable to get RealTek 8139C+ to work with re(4) under FreeBSD 6.1

2006-08-16 Thread Pyun YongHyeon
On Mon, Aug 14, 2006 at 08:03:35PM +0800, Dinesh Nair wrote: > > > On 08/14/06 19:09 Pyun YongHyeon said the following: > >really sucks and need much more CPU power to saturate the link. > >So I don't think it's good idea to make rl(4) serve 8139C+. > > perhaps, but re(4) doesn't work at

[Updated on 2006-8-17] My Linux AIO Implementation Calling for Test

2006-08-16 Thread Intron is my alias in the Internet
Download: http://ftp.intron.ac/tmp/linux_aio-20060817.tar.bz2 Let my patch set keep up with new Linuxolator. From Beijing, China Divacky Roman wrote: On Wed, Aug 09, 2006 at

Re: struct dirent question

2006-08-16 Thread Micah
Tony Maher wrote: Eric Anderson wrote: On 08/16/06 00:49, Tobias Roth wrote: On Tue, Aug 15, 2006 at 10:26:13PM -0500, Eric Anderson wrote: Does the ifdef in the struct dirent (pasted in below) make any sense? Seems like regardless of whether the __BSD_VISIBLE is defined or not, the d_name l

Re: struct dirent question

2006-08-16 Thread Tony Maher
Eric Anderson wrote: > On 08/16/06 00:49, Tobias Roth wrote: > >> On Tue, Aug 15, 2006 at 10:26:13PM -0500, Eric Anderson wrote: >> >>> Does the ifdef in the struct dirent (pasted in below) make any sense? >>> Seems like regardless of whether the __BSD_VISIBLE is defined or not, >>> the d_name len

Re: openospfd

2006-08-16 Thread Yann Berthier
Hello, On Tue, 15 Aug 2006, at 19:59, David Gilbert wrote: > Is there anyone actively working on openospfd (the port)? > > There are systemic things like the fact they want to ignore lo0 > destined routes (although I know how to patch that), but there are > less obvious things that I havn't

Re: exception handling in kernel code

2006-08-16 Thread Stanislav Sedov
Ok, I've finally done it. The module itself is located at http://mbsd.msk.ru/dist/msr-0.1.tar.bz2 port - http://mbsd.msk.ru/dist/devmsr.tar.bz2 Port PR - ports/102158 Now we can use x86info to get all available information about cpu. I could not test amd64 and smp version, so any information (su

Re: struct dirent question

2006-08-16 Thread Joerg Sonnenberger
On Wed, Aug 16, 2006 at 02:45:05PM -0400, Garance A Drosihn wrote: > At 11:31 AM -0500 8/16/06, Eric Anderson wrote: > > > >My point was, that either path you take (if BSD_VISIBLE is > >defined or not), you end up with d_name having a size of > >255 + 1, so what's the point the having it at all? >

Re: struct dirent question

2006-08-16 Thread Eric Anderson
On 08/16/06 13:45, Garance A Drosihn wrote: At 11:31 AM -0500 8/16/06, Eric Anderson wrote: My point was, that either path you take (if BSD_VISIBLE is defined or not), you end up with d_name having a size of 255 + 1, so what's the point the having it at all? To make it clear that d_name is tie

Re: struct dirent question

2006-08-16 Thread Garance A Drosihn
At 11:31 AM -0500 8/16/06, Eric Anderson wrote: My point was, that either path you take (if BSD_VISIBLE is defined or not), you end up with d_name having a size of 255 + 1, so what's the point the having it at all? To make it clear that d_name is tied to the exact value of MAXNAMLEN (just in c

Re: struct dirent question

2006-08-16 Thread Eric Anderson
On 08/16/06 00:49, Tobias Roth wrote: On Tue, Aug 15, 2006 at 10:26:13PM -0500, Eric Anderson wrote: Does the ifdef in the struct dirent (pasted in below) make any sense? Seems like regardless of whether the __BSD_VISIBLE is defined or not, the d_name length will always be 255 + 1. Eric str

Re: Unable to get RealTek 8139C+ to work with re(4) under FreeBSD 6.1

2006-08-16 Thread Pyun YongHyeon
On Mon, Aug 14, 2006 at 06:51:04PM +0800, Dinesh Nair wrote: > > > On 08/14/06 17:22 Dinesh Nair said the following: > > > >i've got a single board computer with VIA C3 Samuel 2, 256MB RAM and 4 > >onboard Realtek 8139C+ NICs. I'm attempting to get FreeBSD 6.1-STABLE > >working on them,

Re: The optimization of malloc(3): FreeBSD vs GNU libc

2006-08-16 Thread Intron is my Internet alias
Jason Evans wrote: (LI Xin) wrote: 2006-08-15 02:38 +0300ladimir Kushnir>>> On -CURENT amd64 (Athlon64 3000+, 512k L2 cache): With jemalloc (without MY_MALLOS): ~/fdtd> /usr/bin/time ./fdtd.FreeBSD 500 500 1000 ... 116.34 real 113.69 user 0.00 sys With MY_MALLOC: ~/fdtd> /