Al,
On Sun, 30 Sep 2001, Alexander Viro wrote:
> Update: fixed a double-free bug in amiga_partition(). After that thing
> seems to be working on Amiga disk sent by Jes (as in, "right amount
> of partitions and reasonably looking boundaries").
>
> Patch is on ftp.math.psu.edu/pub/viro/partition-b-S11-pre1.
Just a random data point: your patch works fine here both with
msdos+extended partitions and with an LDM disk.
I haven't tried the updated patch but as I don't have an amiga it
shouldn't make a difference on my systems anyway...
Best regards,
Anton
--
Anton Altaparmakov <aia21 at cam.ac.uk> (replace at with @)
Linux NTFS maintainer / WWW: http://linux-ntfs.sf.net/
ICQ: 8561279 / WWW: http://www-stu.christs.cam.ac.uk/~aia21/
Does anybody know , what is the maximum number of TCP (http)
terminations/per second a server (single/dual/.. processor) in todays
market can do, without much CPU load. The server would be running linux
kernel 2.4 and apache web server.
Thanks,
Imran.
> Does anybody know , what is the maximum number of TCP (http)
> terminations/per second a server (single/dual/.. processor) in todays
> market can do, without much CPU load. The server would be running linux
> kernel 2.4 and apache web server.
If you are running any kind of high performance connections/second load then
you dont run apache. That isnt what apache is good at
thttpd will do 2000/sec on a decent box. zeus (non free) more, and tux
(kernel http accelerator) holds some records
I am running openssl with apache using modssl. I will have to look at
whether could I use openssl with TUX or zeus.
Thanks.
-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of Alan Cox
Sent: Tuesday, November 06, 2001 3:22 PM
To: [email protected]
Cc: [email protected]
Subject: Re: Linux kernel 2.4 and TCP terminations per second.
> Does anybody know , what is the maximum number of TCP (http)
> terminations/per second a server (single/dual/.. processor) in todays
> market can do, without much CPU load. The server would be running linux
> kernel 2.4 and apache web server.
If you are running any kind of high performance connections/second load then
you dont run apache. That isnt what apache is good at
thttpd will do 2000/sec on a decent box. zeus (non free) more, and tux
(kernel http accelerator) holds some records
Imran> I am running openssl with apache using modssl. I will have
Imran> to look at whether could I use openssl with TUX or zeus.
If you are doing SSL termination without a hardware crypto accelerator
then the cost of the public key operations for the SSL handshake will
far outweigh the cost of TCP termination and the webserver. With a
typical machine (say a 1 GHz P3) I would estimate you could do 200 SSL
handshakes/sec with apache/modssl (with 95% of your CPU time spent in
OpenSSL RSA code). With a hardware crypto accelerator you could get
up to 600-1000 handshakes/sec but the crypto will still be the
bottleneck.
Roland
I am not worried about SSL handshakes/sec. I am looking forward to how much
http/sec I could extract out of a moderate linux box. I have a dell box with
PIII 800 MHz, 256 MB RAM running a very light weight server (which I wrote)
and I wanted to find out how much time does it spend in system for TCP
terminations. The system in running linux kernel version 2.4.2
The server sits in a loop and launches worker threads as it receives a tcp
socket connection. The worker thread then sits in an infinite loop and
sends/receives data from client (which is again a custom client).
I figured out that most of the CPU time was spent in the kernel mode for TCP
terminatiions and Network was not the bottleneck.
-----Original Message-----
From: [email protected]
[mailto:[email protected]]On Behalf Of Roland Dreier
Sent: Tuesday, November 06, 2001 3:44 PM
To: [email protected]
Cc: [email protected]
Subject: Re: Linux kernel 2.4 and TCP terminations per second.
Imran> I am running openssl with apache using modssl. I will have
Imran> to look at whether could I use openssl with TUX or zeus.
If you are doing SSL termination without a hardware crypto accelerator
then the cost of the public key operations for the SSL handshake will
far outweigh the cost of TCP termination and the webserver. With a
typical machine (say a 1 GHz P3) I would estimate you could do 200 SSL
handshakes/sec with apache/modssl (with 95% of your CPU time spent in
OpenSSL RSA code). With a hardware crypto accelerator you could get
up to 600-1000 handshakes/sec but the crypto will still be the
bottleneck.
Roland
from a recent test I just was running with apache on a 1.2GHZ athlon 512MB
ram it looks like it will do ~1800 connections/sec.
just to put the numbers below in perspective :-)
David Lang
On Tue, 6 Nov 2001, Alan Cox wrote:
> > Does anybody know , what is the maximum number of TCP (http)
> > terminations/per second a server (single/dual/.. processor) in todays
> > market can do, without much CPU load. The server would be running linux
> > kernel 2.4 and apache web server.
>
> If you are running any kind of high performance connections/second load then
> you dont run apache. That isnt what apache is good at
>
> thttpd will do 2000/sec on a decent box. zeus (non free) more, and tux
> (kernel http accelerator) holds some records
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
> from a recent test I just was running with apache on a 1.2GHZ athlon 512MB
> ram it looks like it will do ~1800 connections/sec.
>
> just to put the numbers below in perspective :-)
I was doing 2000 a second on a P2/233 just to keep the perspective. I've
not yet hacked thttpd to try Linus new readahead syscall