Samuel Thibault, le sam. 08 mai 2021 21:54:34 +0200, a ecrit:
> Don't bother looking at the existing implementation, its roots dates
> before we really had gsync working.
>
> Sergey Bugaev, le sam. 08 mai 2021 22:35:23 +0300, a ecrit:
> > + do \
> > +{ \
> > + int count; \
> > + cou
Sergey Bugaev, le sam. 08 mai 2021 23:03:34 +0300, a ecrit:
> On Sat, May 8, 2021 at 10:54 PM Samuel Thibault
> wrote:
> > Don't bother looking at the existing implementation, its roots dates
> > before we really had gsync working.
>
> Interesting!
>
> As far as I can see, this implementation w
On Sat, May 8, 2021 at 10:54 PM Samuel Thibault wrote:
> Don't bother looking at the existing implementation, its roots dates
> before we really had gsync working.
Interesting!
As far as I can see, this implementation was committed (by you) in
2018; and gsync has not seen significant changes sin
Hello,
Don't bother looking at the existing implementation, its roots dates
before we really had gsync working.
Sergey Bugaev, le sam. 08 mai 2021 22:35:23 +0300, a ecrit:
> + do \
> +{ \
> + int count; \
> + count = atomic_exchange_and_add_rel (&GL(dl_thread_gscope_count), -1);
>
I've noticed that even a simple hello world does a lot of gsync calls:
$ rpctrace echo hello world |& grep -c gsync
53
These are in fact all identical gsync_wake () calls on a single address:
$ rpctrace echo hello world |& grep gsync | uniq
task132(pid18549)->gsync_wake (202820 0 0);
This immed
