From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] [patch] aux/wacom: prevent "no concurrent reads please" error when moving the pen too fast and support screen tilt
Date: Fri, 16 Apr 2021 11:25:13 +0200 [thread overview]
Message-ID: <CAFSF3XOTad1h4siG7rZyJ_zmer1Dhg7iH4YRYdjMHiG7w5LjSg@mail.gmail.com> (raw)
In-Reply-To: <AB7D4EBB07CA5CC153E00739AF1F7BFF@felloff.net>
yeah, i was wondering if that was the motivation here, esp. in regards
to minimizing user perceived latency.
and if yes i'd be curious if it's actually significant enough to matter.
i can imagine high throughput scenarios, just not mouse input, where
this seems safe to assume even without measuring :D
On 4/15/21, cinap_lenrek@felloff.net <cinap_lenrek@felloff.net> wrote:
>> maybe we need to implement pid reusal...
>
> already done. wrapping pid's should not be a problem.
>
> the main concern is that creating and destroying processes
> has a cost compared to just wake up a existing process.
>
> --
> cinap
>
next prev parent reply other threads:[~2021-04-16 10:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 15:39 james palmer
[not found] ` <b0646909-d59a-4423-8467-32c4c96ef5d3@www.fastmail.com>
2021-04-10 16:49 ` [9front] " james palmer
2021-04-11 15:39 ` [9front] " james palmer
2021-04-12 7:37 ` hiro
2021-04-12 10:00 ` james palmer
2021-04-12 17:03 ` hiro
2021-04-15 21:09 ` cinap_lenrek
2021-04-16 9:25 ` hiro [this message]
2021-04-17 3:32 ` cinap_lenrek
2021-04-24 19:57 ` Michael Enders
2021-04-12 8:12 ` cinap_lenrek
2021-04-12 9:57 ` james palmer
2021-04-19 15:49 ` james palmer
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=CAFSF3XOTad1h4siG7rZyJ_zmer1Dhg7iH4YRYdjMHiG7w5LjSg@mail.gmail.com \
--to=23hiro@gmail.com \
--cc=9front@9front.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).