From: "Henrik Rydberg" <rydberg@euromail.se>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, Jiri Kosina <jkosina@suse.cz>,
Mika Kuoppala <mika.kuoppala@nokia.com>,
Benjamin Tissoires <tissoire@cena.fr>,
Rafi Rubin <rafi@seas.upenn.edu>,
Henrik Rydberg <rydberg@euromail.se>
Subject: [PATCH 0/3] input: evdev: Dynamic buffers (rev2)
Date: Sat, 29 May 2010 17:57:41 +0200 [thread overview]
Message-ID: <1275148664-6238-1-git-send-email-rydberg@euromail.se> (raw)
Ok, second version of the evdev buffer patches.
In the first patch, the locking has been completely reworked. The
buffer locking is now similar to seqlock, except the readers only
block while there is an update affecting the current read. Should be
fairly optimal, but we can always revert to seqlocks in case the
scatter of smp instructions feels inadequate.
The second patch only has trivial changes, and the third patch is
unchanged, but included for completeness.
Cheers,
Henrik
---
Henrik Rydberg (3):
input: evdev: use multi-reader buffer to save space (rev2)
input: evdev: convert to dynamic event buffer (rev2)
input: use driver hint to compute the evdev buffer size
drivers/input/evdev.c | 90 +++++++++++++++++++++++++++++++++---------------
include/linux/input.h | 7 ++++
2 files changed, 69 insertions(+), 28 deletions(-)
next reply other threads:[~2010-05-29 15:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 15:57 Henrik Rydberg [this message]
2010-05-29 15:57 ` [PATCH 1/3] input: evdev: use multi-reader buffer to save space (rev2) Henrik Rydberg
2010-05-29 15:57 ` [PATCH 2/3] input: evdev: convert to dynamic event buffer (rev2) Henrik Rydberg
2010-05-29 15:57 ` [PATCH 3/3] input: use driver hint to compute the evdev buffer size Henrik Rydberg
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=1275148664-6238-1-git-send-email-rydberg@euromail.se \
--to=rydberg@euromail.se \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=mika.kuoppala@nokia.com \
--cc=rafi@seas.upenn.edu \
--cc=tissoire@cena.fr \
/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).