mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: David Herrmann <dh.herrmann@googlemail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] input: Dynamic Minor Numbers
Date: Fri, 21 Sep 2012 13:51:30 -0700	[thread overview]
Message-ID: <2737921.JXTsrgJ0N6@dtor-d630.eng.vmware.com> (raw)
In-Reply-To: <CANq1E4Rcj0UsgQr=0sohXn8rXpY92PMnHAYwXNpsPPFULHQsrw@mail.gmail.com>

On Friday, September 21, 2012 09:18:00 PM David Herrmann wrote:
> Hi Dmitry
> 
> On Fri, Sep 21, 2012 at 11:22 AM, David Herrmann
> 
> <dh.herrmann@googlemail.com> wrote:
> > Hi Dmitry
> > 
> > On Fri, Sep 21, 2012 at 10:07 AM, Dmitry Torokhov
> > 
> > <dmitry.torokhov@gmail.com> wrote:
> >> Thank you very much for working on this, unfortunately your patch extends
> >> the existing infrastructure handling of character devices in input core,
> >> which is quite rigid and sub-optimal.
> >> 
> >> For a while now I wanted to stop input core from pre-creating character
> >> devices and multiplexing file operations and instead push more chardev
> >> handling tasks into individual input handlers and make they more
> >> independent from input core. So while I won't be taking your patch as is
> >> it was a great motivator to finally do something about current
> >> limitation and I would appreciate if you could take a look at the patch
> >> below and see if you have any issues with it.
> > 
> > I didn't know why we did that, anyway. But I tried to keep that logic,
> > even though it is really weird. So I am quite glad that you fixed it.
> 
> Sorry, compiling a kernel takes 44m here so I haven't had time earlier
> this day. But I just recompiled with your patch and it works like a
> charm. I have attached output of "ls -la /dev/input" with 900 uinput
> devices. Performance does suck but that is definitely another issue.

Could you elaborate a bit on this?

> 
> So here's my:
> Tested-by: David Herrmann <dh.herrmann@googlemail.com>

Thanks for testing!

-- 
Dmitry

  reply	other threads:[~2012-09-21 20:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 17:52 David Herrmann
2012-09-20 17:52 ` [PATCH v2 1/3] input: add dynamic-minor allocation helpers David Herrmann
2012-09-20 17:52 ` [PATCH v2 2/3] input: increase INPUT_DEVICES to 512 to allow dynamic minors David Herrmann
2012-09-20 17:52 ` [PATCH v2 3/3] input: evdev: use dynamic-minors if running out of static minors David Herrmann
2012-09-21  8:07 ` [PATCH v2 0/3] input: Dynamic Minor Numbers Dmitry Torokhov
2012-09-21  9:22   ` David Herrmann
2012-09-21 19:18     ` David Herrmann
2012-09-21 20:51       ` Dmitry Torokhov [this message]
2012-09-21 21:32         ` David Herrmann
2012-09-25  8:55   ` David Herrmann

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=2737921.JXTsrgJ0N6@dtor-d630.eng.vmware.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=dh.herrmann@googlemail.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

all inboxes | Powered by JetHome®