[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
I considered the questions that you asked.
Here is another patch that improves the previous one in terms of error
I have checked the queue size is the total number instead of per signal.
my patch can pass the tests here,
which can work as an unit test.
In terms of the sig queue delivery order, for real time signals, I need to
familiar with the
consuming logics in the netbsd code base. I guess maybe we need to sort
real time signals when enqueuing,
or selecting the correct real time signal when consuming.
My action items,
to familiar with signal consuming logic in netbsd, to make sure real time
signals are always consumed based on its signal number (the smaller the
real time signal number, the earlier to be consumed.)
2016-07-15 21:15 GMT-07:00 Charles Cui <charles.cui1984%gmail.com@localhost>:
> Thanks for your feedbacks, I will try to fix these problems as soon as
> Thanks, Charles.
> 2016-07-14 8:20 GMT-07:00 Christos Zoulas <christos%zoulas.com@localhost>:
>> On Jul 14, 5:09pm, charles.cui1984%gmail.com@localhost (Charles Cui) wrote:
>> -- Subject: Re: updates?
>> | Hi Christos,
>> | actually, I have a draft implementation of real time signals,
>> | Let me know if you guys think it is enough (worth to spend time to
>> | it or switch to cross process synchronization).
>> | Here is the commit,
>> There is also the issue of handling sigqueue properly, delivery order,
Main Index |
Thread Index |