From: David Miller <davem@davemloft.net>
To: mahatma@eu.by, mahatma@bspu.unibel.by
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH] cls_u32 u32_classify()
Date: Mon, 18 Feb 2008 21:46:00 -0800 (PST) [thread overview]
Message-ID: <20080218.214600.94322068.davem@davemloft.net> (raw)
In-Reply-To: <47A078AE.6060500@bspu.unibel.by>
From: Dzianis Kahanovich <mahatma@bspu.unibel.by>
Date: Wed, 30 Jan 2008 11:16:30 -0200
> Currently fine u32 "hashkey ... at ..." not work with relative offsets.
> There are simpliest fix to use "eat".
So the question is whether 'sel' is defined to be calculated
before all offsets and EAT operations are processed or before.
I do not understand the U32 classifier enough to know what
this kind of change might or might not break.
Can some u32 expert review this?
Thanks.
next prev parent reply other threads:[~2008-02-19 5:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-30 13:16 [PATCH] cls_u32 u32_classify() Dzianis Kahanovich
2008-02-19 5:46 ` David Miller [this message]
2008-02-19 11:54 ` jamal
2008-02-21 6:43 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2008-01-30 13:31 [PATCH] cls_u32 u32_classify() + Dzianis Kahanovich
2008-01-31 13:30 ` jamal
2008-01-30 13:38 [PATCH] cls_u32 u32_classify() ++ Dzianis Kahanovich
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=20080218.214600.94322068.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=mahatma@bspu.unibel.by \
--cc=mahatma@eu.by \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).