re: mutexes, locks and so on...

2010-11-19 Thread matthew green
> Done. Now I just need to fix hppa so that it will be happy again (as far > as I can tell, that's the only archtecture that defines it's own mutex > operations, apart from VAX). i should see about re-enabling the sparc code at least for UP. please have a look there, too... .mrg.

Re: mutexes, locks and so on...

2010-11-19 Thread Simon Burge
Johnny Billquist wrote: > On 2010-11-20 03:59, Simon Burge wrote: > > Johnny Billquist wrote: > > > >> What I don't get is why it take so much time to even respond to > >> pings, compared to Ultrix or VMS. What are we doing in the kernel??? As > >> usual, I'm open to suggestions... > > > > Have yo

Re: mutexes, locks and so on...

2010-11-19 Thread Johnny Billquist
On 2010-11-20 03:59, Simon Burge wrote: Johnny Billquist wrote: What I don't get is why it take so much time to even respond to pings, compared to Ultrix or VMS. What are we doing in the kernel??? As usual, I'm open to suggestions... Have you tried a profiling kernel? I know that can introdu

Re: mutexes, locks and so on...

2010-11-19 Thread Simon Burge
Johnny Billquist wrote: > What I don't get is why it take so much time to even respond to > pings, compared to Ultrix or VMS. What are we doing in the kernel??? As > usual, I'm open to suggestions... Have you tried a profiling kernel? I know that can introduce its own overheads, but might poin

Re: mutexes, locks and so on...

2010-11-19 Thread Johnny Billquist
On 2010-11-19 13:36, Thor Lancelot Simon wrote: On Fri, Nov 19, 2010 at 01:04:50PM +0100, Johnny Billquist wrote: Doh! Stupid of me. I just realized how mutexes can be taken without ever passing through mutex_enter or mutex_vector_enter, even if they are defined. We also have mutex_tryenter, wh

Re: mutexes, locks and so on...

2010-11-19 Thread Adam Hamsik
On Nov,Friday 19 2010, at 1:04 PM, Johnny Billquist wrote: > On 11/19/10 01:50, Johnny Billquist wrote: >> mutex exit spin with unlock appears to totally have been because some >> spin locks were managed to be taken though mutex_vector_enter, even >> though I have a mutex_spin_enter. I have no id

Re: mutexes, locks and so on...

2010-11-19 Thread Thor Lancelot Simon
On Fri, Nov 19, 2010 at 01:04:50PM +0100, Johnny Billquist wrote: > > Doh! Stupid of me. I just realized how mutexes can be taken without ever > passing through mutex_enter or mutex_vector_enter, even if they are > defined. We also have mutex_tryenter, which cannot be redefined. So make it so

Re: mutexes, locks and so on...

2010-11-19 Thread Johnny Billquist
On 11/19/10 01:50, Johnny Billquist wrote: mutex exit spin with unlock appears to totally have been because some spin locks were managed to be taken though mutex_vector_enter, even though I have a mutex_spin_enter. I have no idea how on earth that path would be possible, but after changing the co

.prop rename

2010-11-19 Thread John Nemeth
The module subsystem has a feature where it can automatically load a .prop file along with the module. The purpose of the file is to store persistent args for the module and/or args for use when the module is autoloaded. It is also being used to store information about the module for use by

genfs_node lock

2010-11-19 Thread Masao Uebayashi
Do I need to take genfs g_glock lock even when read-only mount?