On Dec 3 21:36, Takashi Yano wrote:
> On Mon, 2 Dec 2024 15:25:54 +0100
> Corinna Vinschen wrote:
> > On Nov 29 20:58, Takashi Yano wrote:
> > > On Wed, 27 Nov 2024 17:53:53 +0100
> > > Corinna Vinschen wrote:
> > > Hmmm, just setting THREAD_PRIORITY_NORMAL might be appropriate.
> > > See v3 patch
On Mon, 2 Dec 2024 15:25:54 +0100
Corinna Vinschen wrote:
> On Nov 29 20:58, Takashi Yano wrote:
> > On Wed, 27 Nov 2024 17:53:53 +0100
> > Corinna Vinschen wrote:
> > Hmmm, just setting THREAD_PRIORITY_NORMAL might be appropriate.
> > See v3 patch.
> >
> > > The culprit of the behaviour you're se
On Nov 29 20:58, Takashi Yano wrote:
> On Wed, 27 Nov 2024 17:53:53 +0100
> Corinna Vinschen wrote:
> Hmmm, just setting THREAD_PRIORITY_NORMAL might be appropriate.
> See v3 patch.
>
> > The culprit of the behaviour you're seeing is the fact that *all*
> > cygthread's are running with THREAD_PRIO
On Wed, 27 Nov 2024 17:53:53 +0100
Corinna Vinschen wrote:
> On Nov 26 17:55, Takashi Yano wrote:
> > Previously, the sig thread ran in THREAD_PRIORITY_HIGHEST priority.
> > This causes a critical delay in the signal handling in the main thread
> > if too many signals are received rapidly and the C
On Nov 26 17:55, Takashi Yano wrote:
> Previously, the sig thread ran in THREAD_PRIORITY_HIGHEST priority.
> This causes a critical delay in the signal handling in the main thread
> if too many signals are received rapidly and the CPU is very busy.
> In this case, most of the CPU time is allocated
Previously, the sig thread ran in THREAD_PRIORITY_HIGHEST priority.
This causes a critical delay in the signal handling in the main thread
if too many signals are received rapidly and the CPU is very busy.
In this case, most of the CPU time is allocated to the sig thread, so
the main thread cannot
