From: Dmitry Torokhov <dtor@insightbb.com>
To: Shem Multinymous <multinymous@gmail.com>
Cc: hdaps-devel@lists.sourceforge.net, rlove@rlove.org,
Linux Kernel ML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Michael Riepe <michael@mr511.de>,
Henrique de Moraes Holschuh <hmh@debian.org>
Subject: Re: [Hdaps-devel] [PATCH] hdaps - switch to using input-polldev
Date: Mon, 9 Jul 2007 23:58:07 -0400 [thread overview]
Message-ID: <200707092358.08529.dtor@insightbb.com> (raw)
In-Reply-To: <41840b750707082306n6509ee6ds3a0ccd16b6387353@mail.gmail.com>
On Monday 09 July 2007 02:06, Shem Multinymous wrote:
> > > > Have 2nd input device's ->open() method call input_open_device() for
> > > > the first one.
> > >
> > > Won't that create an overhead by the redundant, unused notifications?
> >
> > They won't leave input core so nothing really noticeable.
>
> Sounds good, then. It's a bit of a hack, but the benefits are well
> worth it (if we can resolve the scheduling issue).
>
You know, I slept on it and I think I want to move the polldev into
opposite direction - to accomodte devices that need "relaxed" polling
and are ok with polling being a bit irregular and maybe even rounded
to next jiffy or something to better accomodate tickless kernels.
So I guess it would be better to drop my hdaps patch after all.
--
Dmitry
next prev parent reply other threads:[~2007-07-10 3:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200705252354.43730.dtor@insightbb.com>
2007-07-09 1:00 ` [Hdaps-devel] [PATCH] hdaps - switch to using input-polldev Shem Multinymous
2007-07-09 3:24 ` Dmitry Torokhov
2007-07-09 4:31 ` Shem Multinymous
2007-07-09 4:53 ` Dmitry Torokhov
2007-07-09 5:29 ` Shem Multinymous
2007-07-09 5:44 ` Dmitry Torokhov
2007-07-09 6:06 ` Shem Multinymous
2007-07-10 3:58 ` Dmitry Torokhov [this message]
2007-07-10 5:56 ` Shem Multinymous
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=200707092358.08529.dtor@insightbb.com \
--to=dtor@insightbb.com \
--cc=akpm@osdl.org \
--cc=hdaps-devel@lists.sourceforge.net \
--cc=hmh@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@mr511.de \
--cc=multinymous@gmail.com \
--cc=rlove@rlove.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.