From: Thomas Graf <tgraf@suug.ch>
To: jamal <hadi@cyberus.ca>
Cc: Patrick McHardy <kaber@trash.net>, netdev <netdev@oss.sgi.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: patch: Action repeat
Date: Wed, 4 May 2005 16:05:40 +0200 [thread overview]
Message-ID: <20050504140540.GE18452@postel.suug.ch> (raw)
In-Reply-To: <1115214782.7665.184.camel@localhost.localdomain>
* jamal <1115214782.7665.184.camel@localhost.localdomain> 2005-05-04 09:53
> On Wed, 2005-04-05 at 15:48 +0200, Thomas Graf wrote:
> > * jamal <1115213600.7665.166.camel@localhost.localdomain> 2005-05-04 09:33
>
> > > in skb_clone() and friends.
> > > Look at CONFIG_NET_CLS_ACT in net/core/skbuff.c
> >
> > Yes this solves the case for dummy devices etc but how would
> > this cause a reset on the way from ingress to egress?
>
> If the verdict is not to reset, there should be no clearing of those
> fields from ingress -> egress until the skb is either freed or someone
> else along the path resets it. Cloning or copying inherits. Am i missing
> something?
I guess not but we might have a different understanding of when to
reset. From my point of view the only reason to reset any meta data
is to provide a certain scope a set of new fresh and clean sheets
to play around. Assuming we define global as everything and local
as per device/(ingress|egress) then we definitely need to invoke
a reset on the way over to egress.
next prev parent reply other threads:[~2005-05-04 14:05 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 16:50 patch: Action repeat jamal
2005-04-30 17:06 ` Patrick McHardy
2005-04-30 17:08 ` Patrick McHardy
2005-04-30 17:27 ` jamal
2005-04-30 18:13 ` Patrick McHardy
2005-04-30 19:51 ` jamal
2005-04-30 20:08 ` Thomas Graf
2005-04-30 20:50 ` jamal
2005-04-30 21:55 ` Thomas Graf
2005-04-30 22:34 ` jamal
2005-04-30 23:58 ` Thomas Graf
2005-05-02 12:10 ` jamal
2005-05-02 15:06 ` Thomas Graf
2005-05-04 11:46 ` jamal
2005-05-04 12:15 ` Patrick McHardy
2005-05-04 12:31 ` Thomas Graf
2005-05-04 12:59 ` jamal
2005-05-04 13:28 ` Thomas Graf
2005-05-04 13:33 ` Thomas Graf
2005-05-04 13:33 ` jamal
2005-05-04 13:48 ` Thomas Graf
2005-05-04 13:53 ` jamal
2005-05-04 14:05 ` Thomas Graf [this message]
2005-05-04 14:23 ` jamal
2005-05-04 14:53 ` Thomas Graf
2005-05-05 13:06 ` jamal
2005-05-01 0:08 ` Patrick McHardy
2005-05-01 0:06 ` Patrick McHardy
2005-05-03 23:28 ` David S. Miller
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=20050504140540.GE18452@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=davem@davemloft.net \
--cc=hadi@cyberus.ca \
--cc=kaber@trash.net \
--cc=netdev@oss.sgi.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).