From: Roberto Nibali <ratz@drugphish.ch>
To: James Morris <jmorris@intercode.com.au>
Cc: linux-kernel@vger.kernel.org, jamal <hadi@cyberus.ca>
Subject: Re: [ANNOUNCE] NF-HIPAC: High Performance Packet Classification
Date: Thu, 26 Sep 2002 22:51:09 +0200 [thread overview]
Message-ID: <3D93733D.6050905@drugphish.ch> (raw)
In-Reply-To: Mutt.LNX.4.44.0209270051180.12285-100000@blackbird.intercode.com.au
> Non-blocking netlink delivery is reliable, although you can overrun the
> userspace socket buffer (this can be detected, however). The fundamental
> issue remains: sending more data to userspace than can be handled.
Agreed.
> A truly reliable transport would also involve an ack based protocol .
> Under certain circumstances (e.g. log every forwarded packet for audit
> purposes), packets would need to be dropped if the logging mechanism
> became overloaded. This would in turn involve some kind of queuing
> mechanism and introduce a new set of performance problems. Reliable
> logging is a challenging problem area in general, probably better suited
> to dedicated hardware environments where the software can be tuned to
> known system capabilities.
Thanks. I think we'll find a solution that will suit us best and if we
have something we let the community know.
Best regards,
Roberto Nibali, ratz
--
echo '[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq'|dc
next prev parent reply other threads:[~2002-09-26 20:44 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 [this message]
2002-09-26 10:25 ` Roberto Nibali
2002-09-26 10:20 ` David S. Miller
2002-09-26 10:49 ` Roberto Nibali
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=3D93733D.6050905@drugphish.ch \
--to=ratz@drugphish.ch \
--cc=hadi@cyberus.ca \
--cc=jmorris@intercode.com.au \
--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