linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nuno Santos <nsantos@edigma.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: David Herrmann <dh.herrmann@googlemail.com>, linux-input@vger.kernel.org
Subject: Re: Interacting with a input kernel driver from user space
Date: Thu, 17 Nov 2011 16:58:36 +0000	[thread overview]
Message-ID: <4EC53D3C.9030900@edigma.com> (raw)
In-Reply-To: <20111116192749.GA26909@core.coreip.homeip.net>

 > Now that i'm copying the proper amount of data I have another
 > problem. I'm actually reading this attribute constantly when I open
 > my control panel, however it seems that I can only have reading
 > results from second to second. Is there anything that limits the
 > amount of times I can push attribute data per second? I would
 > definitily need at least 40 readings per second in order to have my
 > data visualized in control panel.

I had overcome this problem using binary attributes. It's blazing fast now.

First I tried with a 4096 length attribute. But when I tried to transfer 
the whole state variable, the one that size is 40k length, I got kernel 
error at the middle of the transfer. My guess in that case is that the 
operation is not atomic and the variable was written between bin 
attribute read calls. Does this make sense?

Having such an attribute would really spare me a lot of time doing the 
control panel interaction and it would make me windows version and linux 
version very similiar, therefore I would use the very mechanisms.

With this said, i'm not discarding all the thing that you guys I have 
been telling me in the last emails and with the time I can make my head 
clear for structural changes in order to make this become better with 
the time in both OS's.

Thanks,

Nuno

      parent reply	other threads:[~2011-11-17 16:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-14 12:24 Interacting with a input kernel driver from user space Nuno Santos
2011-11-14 15:37 ` David Herrmann
2011-11-14 16:00   ` Nuno Santos
2011-11-14 16:09     ` David Herrmann
2011-11-14 16:31       ` Nuno Santos
2011-11-14 16:58         ` David Herrmann
2011-11-14 18:24           ` Nuno Santos
2011-11-14 18:57             ` Dmitry Torokhov
2011-11-14 23:17               ` Oliver Neukum
2011-11-14 23:34                 ` Dmitry Torokhov
2011-11-15  9:41                   ` Nuno Santos
2011-11-15  9:38                 ` Nuno Santos
2011-11-15  9:35               ` Nuno Santos
2011-11-15 18:23                 ` Dmitry Torokhov
2011-11-15 18:41                   ` Nuno Santos
2011-11-15 19:20                     ` Dmitry Torokhov
2011-11-14 17:13         ` Dmitry Torokhov
2011-11-15 10:32           ` Henrik Rydberg
2011-11-15 10:40             ` Nuno Santos
2011-11-15 19:07             ` Chase Douglas
2011-11-16 10:25               ` Nuno Santos
2011-11-16 10:28                 ` Nuno Santos
2011-11-16 17:28       ` Nuno Santos
2011-11-16 19:27         ` Dmitry Torokhov
2011-11-17 15:39           ` Nuno Santos
2011-11-17 16:58           ` Nuno Santos [this message]

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=4EC53D3C.9030900@edigma.com \
    --to=nsantos@edigma.com \
    --cc=dh.herrmann@googlemail.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=linux-input@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).