From: Ravi Chamarti <ravi_chamarti@yahoo.com>
To: kuznet@ms2.inr.ac.ru, Ravi Chamarti <ravi_chamarti@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Ref: zerocopy +netfilter performance problem.
Date: Thu, 18 Oct 2001 11:41:24 -0700 (PDT) [thread overview]
Message-ID: <20011018184124.57237.qmail@web20901.mail.yahoo.com> (raw)
In-Reply-To: <200110171818.WAA22378@ms2.inr.ac.ru>
Hi,
Thanks for your response Alexey. I appreciate it.
--- kuznet@ms2.inr.ac.ru wrote:
> Hello!
>
> > My question is that is this copy is required for
> > netfilter to work? Do we somehow get around
> > with netfilter to work such that the zerocopy path
> > passes the packet without any copy?
>
> Yes & yes.
>
> Existing netfilter modules do not understand
> fragmented skbs,
> and as soon as netfilter folks are lazy even to move
> the check
> to relevant modules, even smart hooks has to be
> harmed by this.
How many netfilter modules exist which do not
understand fragmented skbs and need to look at the
skb data?
Will the following approach work?
if the somehow hook register shows interest only in
header (by setting a flag, may be in nf_hooks_ops
struct), then we can avoid the copy of the fragmented
skb's data and all other cases, we copy fragmented
skb's data to a kernel buffer. The side effect is that
a flag field is introduced into nf_hook_ops struct
which makes netfilter modules to recompile. Are there
any other side affects or better approaches?
regards
Ravi Chamarti
__________________________________________________
Do You Yahoo!?
Make a great connection at Yahoo! Personals.
http://personals.yahoo.com
next parent reply other threads:[~2001-10-18 18:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200110171818.WAA22378@ms2.inr.ac.ru>
2001-10-18 18:41 ` Ravi Chamarti [this message]
2001-10-18 18:47 ` kuznet
2001-10-16 15:59 sendto syscall is slow Francois Romieu
2001-10-16 16:08 ` Ref: zerocopy +netfilter performance problem Ravi Chamarti
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=20011018184124.57237.qmail@web20901.mail.yahoo.com \
--to=ravi_chamarti@yahoo.com \
--cc=kuznet@ms2.inr.ac.ru \
--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
all inboxes | Powered by JetHome®