Re: Locking etc. (Long, boring, redundant, newbie questions)

2007-03-29 Thread Attilio Rao
2007/3/28, Robert Watson <[EMAIL PROTECTED]>: Pretty much. We disable interrupts for the following reason: as spin mutexes may be acquired in fast interrupt handlers, they may be running on the stack of an existing thread, which may also hold locks. As such, we can't allow the fast handler to a

Re: Locking etc. (Long, boring, redundant, newbie questions)

2007-03-29 Thread Attilio Rao
2007/3/29, Yar Tikhiy <[EMAIL PROTECTED]>: On Wed, Mar 28, 2007 at 10:40:58AM +0100, Robert Watson wrote: > > Spin locks are, FYI, slower than default mutexes. The reason is that they > have to do more work: they not only perform an atomic operation/memory > barrier to set the cross-CPU lock sta

Re: enable/disable in kbd drivers

2007-03-29 Thread Timothy Bourke
Thanks for responding, Max. On Mar 29 at 09:08 -0800, Maksim Yevmenkin wrote: > On 3/24/07, Timothy Bourke <[EMAIL PROTECTED]> wrote in part: > >However, enable is called too many times and disable is never called. > > > >In the kbdmux_ioctl routine: > >KBADDKBD: enable is called via the KBDMU

RE: NVIDIA FreeBSD kernel feature requests

2007-03-29 Thread Thomas Sparrevohn
That is puzzling - I running using on a Nvidia Nforce 590 SLI based machine with no problems using Raid - Mind you this Dell implementation uses only Raid0 - What release are you running? - I have had success With both 6.2, 7.0-Current and AMD-6.2 and AMD-7.0 - On the 64bit there was issues with th

Re: enable/disable in kbd drivers

2007-03-29 Thread Maksim Yevmenkin
On 3/24/07, Timothy Bourke <[EMAIL PROTECTED]> wrote: I have almost finished a ppbus-based driver for Super Nintendo controllers. It presents itself as a keyboard to the operating system. I wanted to start and stop the polling thread via, respectively, the kbd_enable_t and kbd_disable_t hooks, bu

Re: NVIDIA FreeBSD kernel feature requests

2007-03-29 Thread Dag-Erling Smørgrav
"MOUILLE Jean Pierre Ext OF/DT" <[EMAIL PROTECTED]> writes: > Do you plan for a driver for nForce 590sli RAID controller on > FreeBSD ? The disks are recognized but not the RAID arrays. It's not so much a matter of writing a driver as one of teaching the existing driver (ataraid) to recognize the

Re: Locking etc. (Long, boring, redundant, newbie questions)

2007-03-29 Thread Yar Tikhiy
On Wed, Mar 28, 2007 at 10:40:58AM +0100, Robert Watson wrote: > > Spin locks are, FYI, slower than default mutexes. The reason is that they > have to do more work: they not only perform an atomic operation/memory > barrier to set the cross-CPU lock state, but they also have to disable > inter

NVIDIA FreeBSD kernel feature requests

2007-03-29 Thread MOUILLE Jean Pierre Ext OF/DT
Hello, Do you plan for a driver for nForce 590sli RAID controller on FreeBSD ? The disks are recognized but not the RAID arrays. On Motherboard ECS KN3-SLI2, JMicron JMB363 driver is already included in FreeBSD 6.2 (ar0) but in kernel, it goes up to nForce 4. Perhaps have you got later informat

Re: sed -i

2007-03-29 Thread Diomidis Spinellis
Yar Tikhiy wrote: Hi, Recently noticed that our sed(1) differs from its GNU analog in that in -i mode it considers all files as a single sequence of lines while the latter treats each file independently. The in-line mode isn't in POSIX, so it isn't really clear which way is correct. Here is a