[lkml]   [2000]   [Oct]   [25]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: kqueue microbenchmark results
On Wed, Oct 25, 2000 at 01:02:46AM -0500, Jonathan Lemon wrote:

> Yes, someone pointed me to those today. I would suggest reading
> some of the relevant literature before embarking on a design. My
> paper discusses some of the issues, and Mogul/Banga make some good
> points too.
> While an 'edge-trigger' design is indeed simpler, I feel that it
> ends up making the job of the application harder. A simple example
> to illustrate the point: what if the application does not choose
> to read all the data from an incoming packet? The app now has to
> implement its own state mechanism to remember that there may be pending
> data in the buffer, since it will not get another event notification
> unless another packet arrives.

What applications would do better by postponing some of the reading?
I can't think of any reason off the top of my head why an application
wouldn't want to read everything it can. Doing everything in smaller
chunks would increase overhead (but maybe reduce latencies very slightly
-- albeit probably not much when using a get_events()-style interface).

Isn't it probably better to keep the kernel implementation as efficient
as possible so that the majority of applications which will read (and
write) all data possible can do it as efficiently as possible? Queueing
up the events, even as they are in the form received from the kernel, is
pretty simple for a userspace program to do, and I think it's the best
place for it.

I know nothing about any other implementations, though, and I'm speaking
mainly from the experiences I've had with coding daemons using select().
You mention you wrote a paper discussing this issue...Where could I find


[ Stormix Technologies Inc. ][ NetNation Communications Inc. ]
[ ][ ]
[ Opinions expressed are not necessarily those of my employers. ]
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:41    [W:0.154 / U:6.960 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site