From: Christoph Hellwig <hch@infradead.org>
To: Johann Borck <johann.borck@densedata.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: considering kevent - the kernel development process
Date: Tue, 13 Mar 2007 19:06:37 +0000 [thread overview]
Message-ID: <20070313190637.GA900@infradead.org> (raw)
In-Reply-To: <45F6F590.8030909@densedata.com>
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.
next prev parent reply other threads:[~2007-03-13 19:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 19:03 considering kevent - the kernel development process Johann Borck
2007-03-13 19:06 ` Christoph Hellwig [this message]
2007-03-13 20:13 ` Avi Kivity
2007-03-14 13:24 ` Evgeniy Polyakov
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=20070313190637.GA900@infradead.org \
--to=hch@infradead.org \
--cc=johann.borck@densedata.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.