linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willy Tarreau <willy@w.ods.org>
To: Martin Josefsson <gandalf@wlug.westbo.se>
Cc: Willy Tarreau <willy@w.ods.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.4.22-pre10
Date: Sat, 2 Aug 2003 21:14:33 +0200	[thread overview]
Message-ID: <20030802191433.GD13525@alpha.home.local> (raw)
In-Reply-To: <1059848925.1869.22.camel@tux.rsn.bth.se>

On Sat, Aug 02, 2003 at 08:28:46PM +0200, Martin Josefsson wrote:
 
> Uhm, my tests have shown it to be very fast and efficient. But I didn't
> look to see if all packets got through to the logfile. But getting it to
> write logs at ~35MB/s wasn't a problem.

I clearly didn't reach these numbers, I used LOGEMU, and while you're at it,
I must say that when I speak about 1500/s, it's about logs _written_ down.
The firewall can still can process 5k sessions/s, but looses many logs (3.5k
every second).

When I read the LOGEMU code, I had the impression that it was given more as
a proof of concept than anything else. Because there are many many many
"fprintf(of, something_trivial_enough_to_support_memcpy)".

> Did you specify --ulog-qthreshold 50 ?
> and did you specify --ulog-cprange at all? if you don't it will copy the
> entire packet to userspace. I copy 64 bytes to userspace and that's more
> than enough to log everything needed.

honnestly, i't 6 months old in my head, and I don't remember with which
parameters I played. But I'd happily restart a bench if you have some tuning
advices (provided that they are compatible with basic production constraints,
such as log rotation, and a few CPU left for monitoring processes :-))
I cannot promise to to it within a few days though.

Cheers,
Willy


  reply	other threads:[~2003-08-02 19:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-01 16:19 Linux 2.4.22-pre10 Marcelo Tosatti
2003-08-01 22:47 ` Willy Tarreau
2003-08-02  9:42   ` Martin Josefsson
2003-08-02 18:10     ` Willy Tarreau
2003-08-02 18:28       ` Martin Josefsson
2003-08-02 19:14         ` Willy Tarreau [this message]
2003-08-05 12:46   ` Marcelo Tosatti
2003-08-02 13:06 ` Stephan von Krawczynski
2003-08-03 11:01 ` [2.4 patch] fix a compile warning in acpi/system.c Adrian Bunk
2003-08-03 13:16 ` [patch] 2.4.22-pre10: fix circular dependency Adrian Bunk
2003-08-05 20:19   ` Marc-Christian Petersen
2003-08-02  7:26 Linux 2.4.22-pre10 Margit Schubert-While
2003-08-02 12:13 Fridtjof Busse

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=20030802191433.GD13525@alpha.home.local \
    --to=willy@w.ods.org \
    --cc=gandalf@wlug.westbo.se \
    --cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).