Natanael Copa wrote:
> So the test is completely meaningless to verify if gettext will work or
> not
Correct. The only reason that this test is packaged in the gettext tarball
is that gettext needs the 'pthread-once' module, and the unit test of
the 'pthread-once' module (test-pthread-once2.c) nee
On Wed, May 14, 2025 at 06:08:43PM +0200, Bruno Haible wrote:
> Rich Felker wrote:
> > It's using the raw pthread lock and it's completely expected that it
> > fails with >10 cores since there will always be multiple readers
> > scheduled and no chance for a writer to run.
>
> Yes, that's the phen
On Mon, Apr 21, 2025 at 12:20 AM Jaroslav Škarvada wrote:
> > $ { env printf %4095s; env printf %4096s; } > /dev/full
> > printf: write error: Broken pipe
> > printf: write error
> >
> Guys, thanks for the analysis and quick actions. BTW is the Fedora
> help patch which uncovered this
Rich Felker wrote:
> It's using the raw pthread lock and it's completely expected that it
> fails with >10 cores since there will always be multiple readers
> scheduled and no chance for a writer to run.
Yes, that's the phenomenon known as "writer starvation".
> This is necessitated by
> POSIX rw
On Wed, 14 May 2025 10:44:35 -0400
Rich Felker wrote:
> On Wed, May 14, 2025 at 04:15:07PM +0200, Bruno Haible wrote:
> > Rich Felker wrote:
> > > AFAICT the code is in tests/test-lock.c from the gnulib repo and calls
> > > the gl_rwlock_* functions, which should be using the gnulib condvar
> >
On Wed, May 14, 2025 at 04:15:07PM +0200, Bruno Haible wrote:
> Rich Felker wrote:
> > AFAICT the code is in tests/test-lock.c from the gnulib repo and calls
> > the gl_rwlock_* functions, which should be using the gnulib condvar
> > based implementation.
>
> Yes, right. Confirmed by looking at "n
The code of module 'asyncsafe-spin' consists of a multithread-safe spin lock
implementation (that works fine even on native Windows), with an add-on
intented to make it async signal safe (this part does not work reliably on
native Windows).
This suggests that it makes sense to rebase 'asyncsafe-sp
Rich Felker wrote:
> AFAICT the code is in tests/test-lock.c from the gnulib repo and calls
> the gl_rwlock_* functions, which should be using the gnulib condvar
> based implementation.
Yes, right. Confirmed by looking at "nm test-lock".
Bruno
Natanael Copa wrote:
> Note that there are 64 CPU cores. I have only tested with that many cores on
> aarch64.
You could vary the number of CPU cores using the 'taskset' command.
What I see in an Alpine Linux 3.20 / x86_64 VM:
$ time taskset -c 0,1,2,3,4,5,6,7 ./test-pthread-rwlock
real time 0.
On Wed, May 14, 2025 at 02:07:04PM +0200, Natanael Copa wrote:
> [Adding Rich Felker to CC]
>
> On Tue, 13 May 2025 18:05:50 +0200
> Bruno Haible wrote:
>
> > Natanael Copa wrote:
> > > > So, you could try to install a different scheduler by default and repeat
> > > > the test.
> > >
> > > It
[Adding Rich Felker to CC]
On Tue, 13 May 2025 18:05:50 +0200
Bruno Haible wrote:
> Natanael Copa wrote:
> > > So, you could try to install a different scheduler by default and repeat
> > > the test.
> >
> > It passed with chrt --fifo (I had to do it from outside the LXC container):
> >
> >
11 matches
Mail list logo
