From: Fabio Riccardi <fabio@chromium.com>
To: mingo@elte.hu
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Christopher Smith <x@xman.org>,
Andrew Morton <andrewm@uow.edu.au>,
"Timothy D. Witham" <wookie@osdlab.org>,
David_J_Morse@Dell.com
Subject: Re: X15 alpha release: as fast as TUX but in user space
Date: Thu, 03 May 2001 18:58:59 -0700 [thread overview]
Message-ID: <3AF20CE3.63C92B3C@chromium.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0105011906420.2202-100000@localhost.localdomain>
I have fixed the stale header cache problem. Files are statted on every
request, no "practical" tricks.
Performance doesn't seem to have suffered :)
I also have added a cache garbage collector to close "old" file descriptors
and remove even older header cache entries. This should make sure that you
don't exceed your system resources. The definition of old and the sweep
frequency are user configurable.
You can download the new version
from: http://www.chromium.com/X15-Alpha-3.tgz
- Fabio
Ingo Molnar wrote:
> On Tue, 1 May 2001, Fabio Riccardi wrote:
>
> > This is actually a bug in the current X15, I know how to fix it (with
> > negligible overhead) but I've been lazy :)
>
> yep, i think it's pretty straightforward: you have a cache of open file
> descriptors (like Squid i think), and you can start a background 'cache
> synchronization thread' that does a stat() on every open file's real VFS
> path, every second or so. This should have small overhead (the number of
> file descriptors cached should be limited anyway via some sort of LRU),
> and guarantees 'practical coherency', without having the overhead of
> immediate coherency. [total coherency is pointless anyway, not even the
> kernel guarantees it to all parallel VFS users.]
>
> Ingo
next prev parent reply other threads:[~2001-05-04 1:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-28 7:32 X15 alpha release: as fast as TUX but in user space Ingo Molnar
2001-04-29 21:19 ` Fabio Riccardi
2001-05-01 8:53 ` Ingo Molnar
2001-05-01 17:10 ` Fabio Riccardi
2001-05-01 17:12 ` Ingo Molnar
2001-05-04 1:58 ` Fabio Riccardi [this message]
2001-05-04 8:24 ` X15 alpha release Ingo Molnar
2001-05-04 18:07 ` Fabio Riccardi
2001-05-04 8:49 ` X15 alpha release: as fast as TUX but in user space Ingo Molnar
2001-05-04 18:10 ` Fabio Riccardi
2001-05-04 18:38 ` Davide Libenzi
2001-05-09 22:42 ` Fabio Riccardi
2001-05-02 8:50 ` Ingo Molnar
2001-05-02 14:12 ` Zach Brown
2001-05-03 2:41 ` Fabio Riccardi
2001-05-02 23:19 ` Lincoln Dale
2001-05-03 2:29 ` Linux syscall speed -- was X15 rootin-tootin webserver Michael Rothwell
-- strict thread matches above, loose matches on Subject: below --
2001-04-28 0:18 X15 alpha release: as fast as TUX but in user space Fabio Riccardi
2001-04-28 0:41 ` Aaron Lehmann
2001-04-28 0:49 ` David S. Miller
2001-04-28 1:11 ` Fabio Riccardi
2001-04-28 8:42 ` Ingo Molnar
2001-04-28 13:15 ` Ville Herva
2001-04-28 13:21 ` Ingo Molnar
2001-04-28 13:24 ` Ingo Molnar
2001-04-28 13:30 ` Ville Herva
2001-04-28 13:55 ` Andi Kleen
2001-04-29 21:25 ` Fabio Riccardi
2001-04-30 5:43 ` dean gaudet
2001-04-30 6:39 ` David S. Miller
2001-04-30 19:36 ` Fabio Riccardi
2001-04-30 21:47 ` dean gaudet
2001-04-30 21:52 ` David S. Miller
2001-05-01 7:31 ` Ingo Molnar
2001-05-01 7:25 ` Ingo Molnar
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=3AF20CE3.63C92B3C@chromium.com \
--to=fabio@chromium.com \
--cc=David_J_Morse@Dell.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrewm@uow.edu.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=wookie@osdlab.org \
--cc=x@xman.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox