linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: kl@kl.wtf
To: dmitry.torokhov@gmail.com
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Input: evdev - per-client waitgroups
Date: Tue, 06 Oct 2020 09:15:32 +0000	[thread overview]
Message-ID: <0ec848359962ebce267168618b816bb4@kl.wtf> (raw)
In-Reply-To: <20201005233500.GM1009802@dtor-ws>

October 6, 2020 1:35 AM, dmitry.torokhov@gmail.com wrote:

> On Wed, Apr 29, 2020 at 08:41:26PM +0200, Kenny Levinsen wrote:
> 
>> All evdev clients share a common waitgroup. On new input events, this
>> waitgroup is woken once for every client that did not filter the events,
> 
> I am having trouble parsing the changelog (I think I agree with the
> change itself). Did you mean to say "this waitqueue wakes up every
> client, even ones that requested to filter out events that are being
> delivered, leading to duplicated and unwanted wakeups"?

Ah, I suppose my original wording was a bit convoluted. Perhaps the following
is clearer:

	All evdev clients share a common waitgroup. On new input events, all
	clients waiting on this waitgroup are woken up, even those filtering
	out the events, possibly more than once per event. This leads to
	duplicated and unwanted wakeups.

What I tried to say is that not only do all clients polling the device/blocked
on read end up woken up, instead of being woken just once, they are woken once
for every client that was interested in the event.

So, if you have two clients interested and one uninterested, then the shared
waitgroup that all three clients are waiting on is woken up twice in a row.

Should I send an updated patch with the new wording? I'm also fine with your
suggested wording if you prefer that.

Best regards,
Kenny Levinsen

  parent reply	other threads:[~2020-10-06  9:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-29 18:41 [PATCH] Input: evdev - per-client waitgroups Kenny Levinsen
2020-05-29 14:36 ` kl
2020-10-05 23:35 ` dmitry.torokhov
2020-10-06  9:15 ` kl [this message]
2020-10-07  1:35   ` dmitry.torokhov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0ec848359962ebce267168618b816bb4@kl.wtf \
    --to=kl@kl.wtf \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).