On Wed, Feb 20, 2002 at 12:31:53AM +, Tony Finch wrote:
Julian Elischer [EMAIL PROTECTED] wrote:
I can suggest using a netgraph module for the work as it can be connected
to a netgraph ksocket node to receive the requests (jdp made all the
changes needed to allow this to be done).
On Tue, Feb 19, 2002 at 10:00:04AM -0800, Alfred Perlstein wrote:
Disk IO can't be done in a non-blocking manner. If the kernel doesn't
have the portion of the file you wish to read in the buffer cache
then the process will block waiting.
Isn't this exactly what the kqueue mechanism
Tony Finch wrote:
[ ... Terry describes non-blocking I/O on page-not-present
on SVR4, and how it behaves better than BSD ... ]
How does it deal with the situation that the machine's
working set has exceeded memory? If the web server is dealing
with lots of concurrent connections it may
On Monday 18 February 2002 07:54 pm, Peter Wemm wrote:
Mike Silbersack wrote:
On Mon, 18 Feb 2002, Hiten Pandya wrote:
hi all,
As to conclude this thread (for me.), I have come to the decision of
actually starting a project for making a BSD Licensed in-kernel HTTPd
server. The
On Mon, Feb 18, 2002 at 06:54:01PM -0800, Peter Wemm wrote:
Mike Silbersack wrote:
On Mon, 18 Feb 2002, Hiten Pandya wrote:
hi all,
As to conclude this thread (for me.), I have come to the decision of
actually starting a project for making a BSD Licensed in-kernel HTTPd
Apache will switch to this method at some point. I really can't
understand why they went with that complicated pre-forking stuff.
Using non-blockijng I/O is just not that hard.
As mentioned previously, due to the blocking semantics of file I/O on unix,
single process servers will only provide
Hey,
On Tue, Feb 19, 2002 at 09:19:56AM -0800, Kip Macy wrote:
Apache will switch to this method at some point. I really can't
understand why they went with that complicated pre-forking stuff.
Using non-blockijng I/O is just not that hard.
As mentioned previously, due to the blocking
* Dominic Marks [EMAIL PROTECTED] [020219 09:53] wrote:
Hey,
On Tue, Feb 19, 2002 at 09:19:56AM -0800, Kip Macy wrote:
Apache will switch to this method at some point. I really can't
understand why they went with that complicated pre-forking stuff.
Using non-blockijng I/O is just not
On Tue, Feb 19, 2002 at 10:00:04AM -0800, Alfred Perlstein wrote:
* Dominic Marks [EMAIL PROTECTED] [020219 09:53] wrote:
Hey,
On Tue, Feb 19, 2002 at 09:19:56AM -0800, Kip Macy wrote:
Apache will switch to this method at some point. I really can't
understand why they went with
Alfred Perlstein wrote:
Disk IO can't be done in a non-blocking manner. If the kernel doesn't
have the portion of the file you wish to read in the buffer cache
then the process will block waiting. There is simply nothing you
can do about this other than to offload that blocking into another
Julian Elischer [EMAIL PROTECTED] wrote:
I can suggest using a netgraph module for the work as it can be connected
to a netgraph ksocket node to receive the requests (jdp made all the
changes needed to allow this to be done).
Another way would be to implement it as an accept filter which
Dominic Marks [EMAIL PROTECTED]
http://www.acme.com/software/thttpd/notes.html on the section
regarding non-blocking I/O:
The fourth generation. One process only. No non-portable threads/LWPs.
Sends multiple files concurrently using non-blocking I/O, calling
select()/poll()/kqueue() to
Terry Lambert [EMAIL PROTECTED] wrote:
On SVR4, an attempt to access a non-resident page via a
non-blocking fd will result in a fault for that page
being scheduled, while the call returns to the user
process with an EWOULDBLOCK.
A subsequent attempt to read it gets the paged in data,
and
hi all,
As to conclude this thread (for me.), I have come to the decision of
actually starting a project for making a BSD Licensed in-kernel HTTPd
server. The project will be on SourceForge.net.
As you all know, that when starting a project, a name is needed for
project; I completely out of
Hiten Pandya wrote:
As to conclude this thread (for me.), I have come to the decision of
actually starting a project for making a BSD Licensed in-kernel HTTPd
server. The project will be on SourceForge.net.
[ ... ]
To vote, give a +1 for yes, and -1 for no.
o fhttpd (I donno what the
hi all,
As to conclude this thread (for me.), I have come to the decision of=20
actually starting a project for making a BSD Licensed in-kernel HTTPd=20
server. The project will be on SourceForge.net.
I, too, have started one of these, already have it loading, but not doing
anything :)
will it be able to send pages from the filesystem or just preloaded pages?
How will you configure it?
I can suggest using a netgraph module for the work as it can be connected
to a netgraph ksocket node to receive the requests (jdp made all the
changes needed to allow this to be done).
It also
Hi,
On Mon, Feb 18, 2002 at 11:12:54AM -0800, Julian Elischer wrote:
no idea on the name though
forked stick?
It fork's and stick pages out a socket. A graph is a forked stick
diagram. The daemon as a forked stick. And is should be able to serve
more pages than you can shake a forked stick
On Mon, 18 Feb 2002, Hiten Pandya wrote:
hi all,
As to conclude this thread (for me.), I have come to the decision of
actually starting a project for making a BSD Licensed in-kernel HTTPd
server. The project will be on SourceForge.net.
As you all know, that when starting a project, a
On Mon, Feb 18, 2002 at 06:02:54PM +, Hiten Pandya wrote:
If someone has better ideas, please do not hesitate to pass me
your suggestions.
how about: actually write the code before annoying -hackers.
how is JFS coming along...
--
- bill fumerola / [EMAIL PROTECTED] / [EMAIL PROTECTED]
Mike Silbersack wrote:
On Mon, 18 Feb 2002, Hiten Pandya wrote:
hi all,
As to conclude this thread (for me.), I have come to the decision of
actually starting a project for making a BSD Licensed in-kernel HTTPd
server. The project will be on SourceForge.net.
As you all know,
On Mon, 18 Feb 2002, Peter Wemm wrote:
The problem is that our threads implementation sucks. The moment that
thttpd has to do an actual disk read on freebsd, the whole thing comes to a
screeching halt.
Threaded http servers do not stand up to real-world loads on freebsd, unless
there are
22 matches
Mail list logo
