> On Wed, 3 Mar 1999, Oliver Xymoron wrote:
>
> > This is the IPC case - CGI to web server. I/O-Lite accomplishes this one
> > by mapping fragments into the destination's memory space. This means at
> > least a TLB flush, possibly one for each page (or smaller!) of the data
> > the CGI is pumping out.
>
> You take the TLB flush a few times, not every operation. See the bit
> about acls and such -- they set up a pool of shared pages between the
> processes which are reused. You should look at the paper again -- there
> are various subtleties in there.
You're right, I missed that entirely. The window approach makes this look
more attractive. He's a bit terse on the details though - there's only a
paragraph.
> > though. Apache maps entire files at once and keeps a cache of file
> > mappings to minimize this.
>
> Apache doesn't have a cache, it can't do an efficient dynamic cache as a
> multiprocess server... (if you find a solution that works tell us ;)
Funny - I thought I remembered _you_ talking about single Apache processes
keeping multiple mappings around for caching purposes. Maybe I dreamed
that, though I usually don't dream about web servers.
-- "Love the dolphins," she advised him. "Write by W.A.S.T.E.."
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/