Thread (4 messages) 4 messages, 2 authors, 2012-05-05

Re: Deterministic behavior for TTY serial

From: Ivo Sieben <hidden>
Date: 2012-05-02 12:39:08
Also in: linux-serial

Possibly related (same subject, not in this thread)

Hi,
2012/5/2 Ivo Sieben [off-list ref]:
quoted
Hi,

Indeed the lock is only taken for a very short time. So  in most
situations it works fine, the lock is free, and can be taken quickly.
But when I stress my system (e.g. by continuously dumpling a lot of
text data to another serial terminal from the background), my high
priority task sometimes finds the lock is taken. In that case
additional lock handling comes in: priority inheritance, a context
switch to the background task that holds the lock, and a context
switch back after the lock is released again. This makes a normal read
that takes about 50us, to increase in execution time to 150us.
The PREEMPT_RT uses mutexes for "normal" spin locks that do not
disable interrupts...
I'll try to use raw spinlocks in this code section and for the tty flip buffer
See if that can solve my problem.

If you have other ideas... let me know!

Regards,
Ivo
--
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help