public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 01 May 2001 10:10:53 -0700	[thread overview]
Message-ID: <3AEEEE1D.F0C4F1F6@chromium.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0105011047540.4266-100000@localhost.localdomain>

This is actually a bug in the current X15, I know how to fix it (with
negligible overhead) but I've been lazy :)

give me a few days...

 - Fabio

Ingo Molnar wrote:

> hm, another X15 caching artifact i noticed: i've changed the index.html
> file, and while X15 was still serving the old copy, TUX served the new
> file immediately.
>
> its cache is apparently not coherent with actual VFS contents. (ie. it's a
> read-once cache apparently?) TUX has some (occasionally significant)
> overhead due to non-cached VFS-lookups.
>
>         Ingo
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


  reply	other threads:[~2001-05-01 17:07 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 [this message]
2001-05-01 17:12       ` Ingo Molnar
2001-05-04  1:58         ` Fabio Riccardi
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=3AEEEE1D.F0C4F1F6@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