> > >>- it's more adapted for use in real-time environments
> > >>
> > >I still do not see why you are stating this. Why do you say this?
> > >
> > Due to possible priority inversion problems in David's core.
>
> I am still not convinced of your statements here, sorry. Specifics
> please.
So, again, David's write_then_read function which is the basic one for all the synchronous
transfers uses single static pointer to kmalloc'ed buffer and protects its usage by
semaphores. If there are multiple controllers onboard, this serialization is suboptimal
and may cause priority inversion if, for instance, two threads with different priorities
will use this function at the same time.
Vitaly
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
