From: Thomas Graf <tgraf@suug.ch>
To: jamal <hadi@cyberus.ca>
Cc: Patrick McHardy <kaber@trash.net>, netdev@oss.sgi.com
Subject: Re: [RFC] meta ematch
Date: Sun, 16 Jan 2005 17:49:05 +0100 [thread overview]
Message-ID: <20050116164905.GX26856@postel.suug.ch> (raw)
In-Reply-To: <1105892360.1091.655.camel@jzny.localdomain>
* jamal <1105892360.1091.655.camel@jzny.localdomain> 2005-01-16 11:19
> > > I am not sure iam following yet:
> > >
> > > So in the case of indev, you would need to
> > > - get indev ifindex from skb
> > > - get indev name from skb
> > > - compare the two??
> > >
>
> Can you explain the above in context of indev = "eth0"? I am still not
> sure i get it:
>
> + if (meta_get(skb, info, &meta->lvalue, &l_value) < 0 ||
> + meta_get(skb, info, &meta->rvalue, &r_value) < 0)
> + return 0;
> + r = meta_type_ops(&meta->lvalue)->compare(&l_value, &r_value);
Sure, indev = "eth0"
TCA_EM_META_HDR = {
.left = {
.kind = TCF_META_TYPE_VAR << 12 | TCF_META_ID_INDEV,
.op = TCF_EM_EQ,
},
.right = {
.kind = TCF_META_TYPE_VAR << 12 | TCF_META_ID_VALUE,
},
};
TCA_EM_META_LVALUE = EMPTY; /* unused */
TCA_EM_META_RVALUE = "eth0"
The configuration part will transform this into:
struct meta_match = {
.lvalue = {
.hdr = {
.kind = TCF_META_TYPE_VAR << 12 | TCF_META_ID_INDEV,
.op = TCF_EM_EQ,
},
},
.rvalue = {
.hdr = {
.kind = TCF_META_TYPE_VAR << 12 | TCF_META_ID_VALUE,
}
.val = strdup("eth0"),
.len = strlen("eth0"),
},
}
meta_get will make meta_obj's out of it:
struct meta_obj l_value = {
.value = dev->name,
.len = strlen(dev->name),
},
struct meta_obj r_value = {
.value = "eth0",
.len = strlen("eth0"),
}
the type specific compare will compare these.
next prev parent reply other threads:[~2005-01-16 16:49 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-03 12:56 [RFC] ematch API, u32 ematch, nbyte ematch, basic classifier Thomas Graf
2005-01-04 4:13 ` jamal
2005-01-04 12:03 ` Thomas Graf
2005-01-04 13:19 ` jamal
2005-01-04 13:46 ` Thomas Graf
2005-01-04 12:27 ` Thomas Graf
2005-01-04 13:22 ` jamal
2005-01-04 13:41 ` Thomas Graf
2005-01-05 2:54 ` jamal
2005-01-05 11:09 ` Thomas Graf
2005-01-04 22:36 ` Thomas Graf
2005-01-05 3:12 ` jamal
2005-01-05 11:00 ` Thomas Graf
2005-01-05 13:33 ` jamal
2005-01-05 14:45 ` Thomas Graf
2005-01-05 16:48 ` Thomas Graf
2005-01-06 14:03 ` jamal
2005-01-06 13:47 ` jamal
2005-01-06 19:41 ` Thomas Graf
2005-01-07 13:45 ` jamal
2005-01-08 14:54 ` Thomas Graf
2005-01-10 13:26 ` jamal
2005-01-10 21:17 ` Thomas Graf
2005-01-10 22:05 ` jamal
2005-01-10 23:30 ` Thomas Graf
2005-01-13 17:41 ` [RFC] meta ematch Thomas Graf
2005-01-13 18:54 ` Patrick McHardy
2005-01-13 19:20 ` Thomas Graf
2005-01-14 1:13 ` Patrick McHardy
2005-01-14 15:14 ` Thomas Graf
2005-01-16 14:58 ` jamal
2005-01-16 15:09 ` Thomas Graf
2005-01-16 15:37 ` jamal
2005-01-16 15:57 ` Thomas Graf
2005-01-16 16:19 ` jamal
2005-01-16 16:49 ` Thomas Graf [this message]
2005-01-16 16:11 ` jamal
2005-01-16 16:32 ` Thomas Graf
2005-01-16 17:18 ` jamal
2005-01-16 18:47 ` Thomas Graf
2005-01-16 16:32 ` Patrick McHardy
2005-01-16 17:24 ` jamal
2005-01-05 13:32 ` [RFC] ematch API, u32 ematch, nbyte ematch, basic classifier Florian Weimer
2005-01-05 13:45 ` jamal
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=20050116164905.GX26856@postel.suug.ch \
--to=tgraf@suug.ch \
--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).