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  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 26 Feb 2012 10:05:59 -0500
From:	Richard Yao <>
To:	Bernd Petrovitsch <>
CC:	Henrik Rydberg <>,
	Bobby Powers <>, Ted Ts'o <>,
	Greg KH <>,
	Guenter Roeck <>,
	Jidong Xiao <>,
	Kernel development list <>
Subject: Re: Can we move device drivers into user-space?

>> I do not see what prevents an in-kernel context switch into a ring 3
>> context with a different process address space. Is it necessary to
>> remove the code from the kernel tree before someone can do this?
> No, and that's the real problem here: Everybody who might think it's a
> good idea may please implement - and thus propose - something concrete,
> try it out and comeback with experience and performance numbers - and
> not just try to come up with some theory and other misleading points
> (what political aspect?!) and ideas what others should do and why it
> might be better.

It seems counterproductive to tell people to produce results without
doing the brainstorming that such results require.

If such discussion is not welcome here, then the FreeBSD project has a
similar kernel design. Perhaps it would be more productive for those
interested in this to brainstorm on their mailing list. If anything
materializes, it could be for their kernel instead. Nothing is forcing
anyone to do things with Linux.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists