update on running FreeBSD on xen

2006-01-03 Thread Kip Macy
The curious can track its status (known bugs, feature plans, release plans, etc.) at: http://www.fsmware.com/xenofreebsd/7.0/STATUS It is in perforce under //depot/projects/xen3 ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailma

Re: An idea of remove MUTEX_WAKE_ALL

2006-01-03 Thread Scott Long
Daniel Eischen wrote: On Tue, 3 Jan 2006, Scott Long wrote: for a bit if the current lock owner is running on another CPU? Do we currently do that? (*) No, I am not referring to spin mutexes. Adaptive mutexes are enabled by default and have been for at least a year. Ahh, then that's wh

Re: An idea of remove MUTEX_WAKE_ALL

2006-01-03 Thread Daniel Eischen
On Tue, 3 Jan 2006, Scott Long wrote: > > for a bit if the current lock owner is running on another CPU? > > Do we currently do that? > > > > (*) No, I am not referring to spin mutexes. > > > > Adaptive mutexes are enabled by default and have been for at least a > year. Ahh, then that's what they

Re: An idea of remove MUTEX_WAKE_ALL

2006-01-03 Thread Scott Long
Daniel Eischen wrote: On Tue, 3 Jan 2006, John Baldwin wrote: On Sunday 01 January 2006 02:21 am, prime wrote: Hi hackers, I have an idea about remove the kernel option MUTEX_WAKE_ALL. When we unlock the mutex(in _mtx_unlock_sleep),we can directly give the lock to the first thread waiti

Re: An idea of remove MUTEX_WAKE_ALL

2006-01-03 Thread Daniel Eischen
On Tue, 3 Jan 2006, John Baldwin wrote: > On Sunday 01 January 2006 02:21 am, prime wrote: > > Hi hackers, > >I have an idea about remove the kernel option MUTEX_WAKE_ALL. > >When we unlock the mutex(in _mtx_unlock_sleep),we can directly > > give the lock to the first thread waiting on the

Re: An idea of remove MUTEX_WAKE_ALL

2006-01-03 Thread John Baldwin
On Sunday 01 January 2006 02:21 am, prime wrote: > Hi hackers, >I have an idea about remove the kernel option MUTEX_WAKE_ALL. >When we unlock the mutex(in _mtx_unlock_sleep),we can directly > give the lock to the first thread waiting on the turnstile.And a > thread gets the mutex after he r

Re: Problem about libnet on FreeBSD 6.0

2006-01-03 Thread Gilbert Fernandes
> The problem is that libnet defines ether_addr without regard for the fact > that it's defined in our system headers. This is a bug in libnet, not > FreeBSD. Very interesting information :) Thanks for your reply (and happy new year !) -- unzip ; strip ; touch ; grep ; finger ; mount ; fsck ; m

devfs

2006-01-03 Thread TSaplin Mikhail
Hi all i have a problem with devfs device hiding. My system is FreeBSD 6.0 (i386 and amd64, compiled from last sunday source (RELENG_6)) After mounting defs: #mount -t devfs devfs /tmp/proba first devfs command: # devfs -m /tmp/proba rule add type disk hide devfs rule: ioctl DEVFSIO_RADD: Input/