Re: Deterministic behavior for TTY serial

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

 



Hi,

> 2012/5/2 Ivo Sieben <meltedpianoman@xxxxxxxxx>:
>> 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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Kernel Newbies]     [Security]     [Netfilter]     [Bugtraq]     [Linux PPP]     [Linux FS]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Samba]     [Video 4 Linux]     [Linmodem]     [Device Mapper]     [Linux Kernel for ARM]

  Powered by Linux