From: "xinhui.pan" <xinhuix.pan@intel.com>
To: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
Cc: Peter Hurley <peter@hurleysoftware.com>,
Greg KH <gregkh@linuxfoundation.org>, mnipxh <mnipxh@gmail.com>,
jslaby@suse.cz, linux-kernel@vger.kernel.org,
yanmin_zhang@linux.intel.com
Subject: Re: [PATCH] tty/tty_io.c: make a check before reuse cdev
Date: Thu, 24 Jul 2014 19:01:46 +0800 [thread overview]
Message-ID: <53D0E79A.20201@intel.com> (raw)
In-Reply-To: <20140723170753.5e2047c5@alan.etchedpixels.co.uk>
于 2014年07月24日 00:07, One Thousand Gnomes 写道:
>> Very nice solution. We will check if this can cause any risk, both to kernel and user space.
>> Using a new tty base to register with new cdevs may give us more chance to wait PROCESS quit/close.
>> when total 256 tty used up, what we should do is still in discuss.
>
> At that point you may want to look at how fuser works and create some
> kind of policy manager needs to kill problem tasks owning a device.
>
> Or in theory there is no reason nowdays we can't go above 256 devices -
> in theory 8)
>
hi, Alan
Thanks for your nice comments.
In theory it can go over 256 devices, In fact, it will waste more memories. :)
We really need a policy manager that works well.
FT guys may offer it one day. it's a little long time maybe. :(
When I was a student, I heard you leave from kernel.
Welcome back to kernel, I didn't know that you are back. So sorry.
> Alan
>
>
next prev parent reply other threads:[~2014-07-24 11:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-21 12:47 [PATCH] tty/tty_io.c: make a check before reuse cdev pp
2014-07-21 15:38 ` Greg KH
2014-07-22 11:52 ` xinhui.pan
2014-07-22 16:40 ` Peter Hurley
2014-07-22 17:38 ` Greg KH
2014-07-23 9:21 ` xinhui.pan
2014-07-23 16:04 ` Peter Hurley
2014-07-24 10:23 ` xinhui.pan
2014-07-25 15:24 ` xinhui
2014-07-23 16:07 ` One Thousand Gnomes
2014-07-24 11:01 ` xinhui.pan [this message]
2014-07-24 11:03 ` xinhui.pan
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=53D0E79A.20201@intel.com \
--to=xinhuix.pan@intel.com \
--cc=gnomes@lxorguk.ukuu.org.uk \
--cc=gregkh@linuxfoundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mnipxh@gmail.com \
--cc=peter@hurleysoftware.com \
--cc=yanmin_zhang@linux.intel.com \
/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