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: <20070313190637.GA900@infradead.org>
Date:	Tue, 13 Mar 2007 19:06:37 +0000
From:	Christoph Hellwig <hch@...radead.org>
To:	Johann Borck <johann.borck@...sedata.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: considering kevent - the kernel development process

please cut your cc lines next time, thanks.

On Tue, Mar 13, 2007 at 08:03:44PM +0100, Johann Borck wrote:
> if the next section seems obvious, please skip it
> -------------------------------------------------------------------------
> There is a need for a generic event handling mechanism in Linux - maybe 
> it is enough to cite the current CGL Performance Requirements Definition
> Version 4.0 at
> http://developer.osdl.org/dev/cgl/cgl40/cgl40-performance.pdf , page 13:
> 
> PRF.5.0     Efficient Low-Level Asynchronous Events  Priority P1            
> Description: OSDL CGL specifies that carrier grade Linux shall provide 
> an efficient capability for handling a large number of essentially 
> simultaneous asynchronous events arriving on multiple channels, such as
> multiple sockets or other similar paths. This mechanism is needed to 
> enforce system scalability and soft real-time responsiveness by
> reducing contentions appearing at the kernel level, especially under 
> high load.

It's not obvious, but utter bullshit.  Please go away if you think
starting post with quotes from CGL specs is even remotely close to
a good idea.

-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ