Re: Why no trylock for read/write_bh?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



> sounds like u need a mutex or semaphore lock.   not the spinlock type,
> nevertheless, pick your choice:
>
> c06f5040 T _read_trylock
> c06f5028 T _spin_trylock
> c06f5154 T _spin_trylock_bh
> c06f5061 T _write_trylock
> c0444958 T down_read_trylock
> c0444ec4 T down_trylock
> c0444978 T down_write_trylock
> c06f4096 T mutex_trylock
> c044e86e t rt_mutex_slowtrylock
> c06f4844 T rt_mutex_trylock
> c067ccc2 T rtnl_trylock

Thank you, I will look into those.

>
> but sorry, why "proc-variable" need bh-kind of lock?

When reading/writing to a proc-variable, a softirq is triggered. And since
the read/write-functions of my proc variable is accsessing a shared value,
I need to have locks that disable softirqs for the time being.

-Kristian


--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ


[Index of Archives]     [Newbies FAQ]     [Linux Kernel Mentors]     [Linux Kernel Development]     [IETF Annouce]     [Git]     [Networking]     [Security]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux SCSI]     [Linux ACPI]
  Powered by Linux