From: Doohwan Lee <letsme@gmail.com>
To: Anupam Kapoor <anupam.kapoor@gmail.com>
Cc: Shyam Shrivastav <shrivastav.shyam@gmail.com>, users@dpdk.org
Subject: Re: [dpdk-users] Question about range type of DPDK ACL
Date: Wed, 21 Jun 2017 20:24:06 +0900 [thread overview]
Message-ID: <CAG5unGy2MZ7RcoDqtX138MfRqf36167YOpLyEACD26ei0Ymh9w@mail.gmail.com> (raw)
In-Reply-To: <CAEXHiZEWL0AgCjC9ncGN2P=PiRX4U8OAFYYWq+5BL2OChzrVEQ@mail.gmail.com>
Yes. you are right. I also already knew that 32bit match with mask type
works well.
My point is 32bit match with 'range type' doesn't work in some case.
On Wed, Jun 21, 2017 at 6:46 PM, Anupam Kapoor <anupam.kapoor@gmail.com>
wrote:
>
> On Wed, Jun 21, 2017 at 11:36 AM, Doohwan Lee <letsme@gmail.com> wrote:
>
>> DPDK ACL library uses multi-bit trie with 8-bit stride.
>> I guess that implementation of the trie doesn't support 32bit range
>> matching.
>>
>
> well, you _can_ have address wildcard matches e.g. an address+mask
> combination of 1.2.3.0/24 would match all addresses 1.2.3.[0..255]
>
> --
> kind regards
> anupam
>
> In the beginning was the lambda, and the lambda was with Emacs, and Emacs
> was the lambda.
>
next prev parent reply other threads:[~2017-06-21 11:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-20 8:27 이두환
2017-06-20 8:58 ` Shyam Shrivastav
2017-06-21 0:50 ` 이두환
2017-06-21 5:11 ` Shyam Shrivastav
2017-06-21 6:06 ` Doohwan Lee
2017-06-21 9:46 ` Anupam Kapoor
2017-06-21 11:24 ` Doohwan Lee [this message]
2017-06-21 12:09 ` Shyam Shrivastav
2017-06-22 2:27 ` Doohwan Lee
2017-06-22 4:26 ` Shyam Shrivastav
2017-06-22 5:58 ` Doohwan Lee
2017-06-22 6:12 ` Anupam Kapoor
2017-06-22 6:27 ` Shyam Shrivastav
2017-06-22 6:58 ` Doohwan Lee
2017-06-22 7:12 ` Shyam Shrivastav
2017-06-22 7:27 ` Doohwan Lee
2017-06-22 8:31 ` Shyam Shrivastav
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=CAG5unGy2MZ7RcoDqtX138MfRqf36167YOpLyEACD26ei0Ymh9w@mail.gmail.com \
--to=letsme@gmail.com \
--cc=anupam.kapoor@gmail.com \
--cc=shrivastav.shyam@gmail.com \
--cc=users@dpdk.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).