linux-kernel - Re: Can we move device drivers into user-space?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120224201655.GA5994@kroah.com>
Date:	Fri, 24 Feb 2012 12:16:55 -0800
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Henrik Rydberg <rydberg@...omail.se>
Cc:	Guenter Roeck <guenter.roeck@...csson.com>,
	Jidong Xiao <jidong.xiao@...il.com>,
	Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: Can we move device drivers into user-space?

On Fri, Feb 24, 2012 at 09:10:27PM +0100, Henrik Rydberg wrote:
> I am not complaining about the kernel and its driver structure - on
> the contrary. I do, however, see a reason why constructing lower-level
> interfaces to userspace may be of benefit. The kernel is growing
> tremendously fast. Sooner or later, parts of the present driver
> responsibility will have to be split into smaller chunks. Why not
> place those chunks outside the kernel itself?

I fail to understand why you think the growth of the kernel will require
drivers to be split into chunks in the future.  Are we somehow growing
faster than is required / needed / wanted and outstripping the size of
what we are allowed to take up on machines?

greg k-h
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/