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: Wed, 09 May 2001 15:42:26 -0700 [thread overview]
Message-ID: <3AF9C7D2.1E2BD87C@chromium.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0105041028430.2178-100000@localhost.localdomain>
Hello,
I have uploaded a new release of X15 that hopefully solves all the RFC bugs.
I say hopefully because I haven't had the opportunity to fully test the
request pipelining. Is there anything to automatize such tests?
>From what I could measure X15 is still a good 5% faster than TUX.
You can find the file at: http://www.chromium.com/X15-Alpha-4.tgz
BTW: Next release (in a week or so) will be a beta and it will include source
code!
BTW2: I'll be away from my email in the next few days, so don't be amazed if
I'll be kind of slow replying to messages...
- Fabio
Ingo Molnar wrote:
> yet another anomaly i noticed. X15 does not appear to handle pipelined
> HTTP/1.1 requests properly, it ignores the second request if two requests
> arrive in the same packet.
>
> SPECweb99 does not send pipelined requests, but a number of RL web clients
> do. (Mozilla, apt-get, etc.)
>
> 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/
next prev parent reply other threads:[~2001-05-09 22:38 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
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 [this message]
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=3AF9C7D2.1E2BD87C@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