lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Mon, 20 Jun 2011 16:27:41 +0200
From:	Monica Puig-Pey <puigpeym@...can.es>
To:	<linux-rt-users@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: synchronization mechanisms


Hello!
As I told you in previous questions I'm developing drivers using the 
2.6.31-11-rt patch under ubuntu 10.04.
It is very important for me to know about which real time 
synchronization mechanisms do I have.
I found the RT-mutexes, with priority inherintance, the plists (priority 
lists) and now I'm looking for more information about semaphores. I 
haven't found anything relevant in the code that I could know that they 
work well under real time, having a priority queue of tasks waiting on 
it. So I've made an easy example where I have 3 kernel threads with 
different priorities each (60,70,80) in the semaphore queue. Then I see 
is always the most priority kthread who wakes up the first. Good! It 
seems to work as a RT semaphore!
In my code I have an error. I can use down_interruptible but I can't use 
down_killable. Why is it?
Could anybody give me some help about semaphores in the rt-patch and 
about any other synchronization mechanism thought for real time?

Thanks a lot

Mónica
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ