All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Kegel <dank@kegel.com>
To: Ken Brownfield <brownfld@irridia.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: tux officially in kernel?
Date: Fri, 15 Feb 2002 08:37:14 -0800	[thread overview]
Message-ID: <3C6D393A.92BBD4CF@kegel.com> (raw)

Ken Brownfield wrote:
> The problem with X15 is that it's unavailable.  I've tried for months
> and months to get someone at that company to respond or get a copy to
> try.  Also, is it GPL?  Free?

I have a copy -- they sent one to me readily back when it was new --
but it's not open source, so I can't share it.
It's not a huge program; the whole thing is 5000 lines of C.
It uses the rtsignal method of readiness notification.

IMHO anyone writing a similar user-space server these days should start 
with a clean encapsulation of the readiness notification code, e.g. http://www.kegel.com/dkftpbench/doc/Poller.html .
The performance would be similar, the code would be
a lot cleaner, and it'd be a heck of a lot more portable.

> As for TUX, I would certainly prefer user-space if it was indeed as fast
> in all cases.  But I don't think X15 is really a factor in TUX's
> inclusion.  I'd say replacing khttpd with TUX2 is a no-brainer unless
> X15's performance has been proven and it's GPL.  And while khttpd is an
> interesting example, it really rocks at small image serving.  I've had
> it in production since 2.4.0-test1.

Point taken.  One of my friends uses khttpd in production, too.

Somebody needs to come up with a nice GPL'd userspace replacement
for khttpd.  (Or does one already exist?  I haven't been following things
too closely...)

- Dan

             reply	other threads:[~2002-02-15 16:30 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-15 16:37 Dan Kegel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-11 12:49 tux officially in kernel? Roy Sigurd Karlsbakk
2002-02-11 16:36 ` J Sloan
2002-02-13 13:58   ` john slee
2002-02-14 23:33     ` J Sloan
2002-02-14 23:54       ` Robert Love
2002-02-15  1:00         ` Ken Brownfield
2002-02-15 12:36           ` john slee
2002-02-15 21:11         ` David Lang
2002-02-15 21:35           ` Benny Sjostrand
2002-02-15 23:48             ` Luigi Genoni
2002-02-16 18:59     ` Jason Czerak
2002-02-16 19:25       ` jjs

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=3C6D393A.92BBD4CF@kegel.com \
    --to=dank@kegel.com \
    --cc=brownfld@irridia.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.