From: Roberto Nibali <ratz@drugphish.ch>
To: "David S. Miller" <davem@redhat.com>
Cc: ak@suse.de, niv@us.ibm.com, linux-kernel@vger.kernel.org,
hadi@cyberus.ca
Subject: Re: [ANNOUNCE] NF-HIPAC: High Performance Packet Classification
Date: Thu, 26 Sep 2002 12:49:26 +0200 [thread overview]
Message-ID: <3D92E636.1010404@drugphish.ch> (raw)
In-Reply-To: 20020926.032031.76775895.davem@redhat.com
> What if the netconsole packets cause events to be logged?
Oups! Well, you could send them via printk to the internal printk buffer
which then gets fetched by the local syslog and then you can decide what
to do since those messages should never fill up the buffer as quickly as
syslog will be able to get them. Actually then you should rate limit the
printk messages and probably also increase the buffer size.
But to be honest, those are not the usual messages that fill up the
buffer so fast that syslog is not able to read the message before the
buffer gets overwritten again. Of course you will then have a logfile
inconsistency and this could be accounted just as well as a loss of trace.
But generally I agree that you're standing there pants down. For example
if you have a filter rule in the routing or whereever code that doesn't
permit the packets to leave the machine and thus to be dropped. Ah well
... it was worth a try.
[Hmpf, my collegue is just testing this right now but I think I can then
tell him to stop this because you're always biting your own tail with
this approach, one way or another].
Thanks for the valuable input and best regards,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
next prev parent reply other threads:[~2002-09-26 10:43 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3D924F9D.C2DCF56A@us.ibm.com.suse.lists.linux.kernel>
[not found] ` <20020925.170336.77023245.davem@redhat.com.suse.lists.linux.kernel>
2002-09-26 0:31 ` [ANNOUNCE] NF-HIPAC: High Performance Packet Classification Andi Kleen
2002-09-26 0:29 ` David S. Miller
2002-09-26 0:46 ` Andi Kleen
2002-09-26 0:44 ` David S. Miller
2002-09-26 9:00 ` Roberto Nibali
2002-09-26 9:06 ` David S. Miller
2002-09-26 9:24 ` Roberto Nibali
2002-09-26 9:21 ` David S. Miller
2002-09-26 15:13 ` James Morris
2002-09-26 20:51 ` Roberto Nibali
2002-09-26 10:25 ` Roberto Nibali
2002-09-26 10:20 ` David S. Miller
2002-09-26 10:49 ` Roberto Nibali [this message]
2002-09-26 12:03 ` jamal
2002-09-26 20:23 ` Roberto Nibali
2002-09-27 13:57 ` jamal
2002-09-26 12:04 ` Andi Kleen
2002-09-26 20:49 ` Roberto Nibali
2002-09-30 17:36 ` Bill Davidsen
2002-10-02 17:37 ` Roberto Nibali
2002-09-26 1:17 ` Nivedita Singhvi
2002-09-26 1:15 ` Andi Kleen
2002-09-26 0:06 Nivedita Singhvi
2002-09-26 0:03 ` David S. Miller
2002-09-26 0:50 ` Nivedita Singhvi
2002-09-26 0:40 ` David S. Miller
2002-09-26 1:09 ` Nivedita Singhvi
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=3D92E636.1010404@drugphish.ch \
--to=ratz@drugphish.ch \
--cc=ak@suse.de \
--cc=davem@redhat.com \
--cc=hadi@cyberus.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=niv@us.ibm.com \
/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).