Algorithms for Packet Classification Pankaj Gupta and Nick Mckeown, Stanford University

Total Page:16

File Type:pdf, Size:1020Kb

Algorithms for Packet Classification Pankaj Gupta and Nick Mckeown, Stanford University Algorithms for Packet Classification Pankaj Gupta and Nick McKeown, Stanford University Abstract The process of categorizing packets into “flows” in an Internet router is called packet classification. All packets belonging to the same flow obey a predefined rule and are processed in a similar manner by the router. For example, all packets with the same source and destination IP addresses may be defined to form a flow. Packet classification is needed for non-best-effort services, such as firewalls and quality of service; services that require the capability to distinguish and isolate traffic in differ- ent flows for suitable processing. In general, packet classification on multiple fields is a difficult problem. Hence, researchers have proposed a variety of algorithms which, broadly speaking, can be categorized as basic search algorithms, geometric algorithms, heuristic algorithms, or hardware-specific search algorithms. In this tutorial we describe algorithms that are representative of each category, and discuss which type of algorithm might be suitable for different applications. ntil recently, Internet routers provided only best- Table 2 shows the flows into which an incoming packet effort service, servicing packets in a first-come- must be classified by the router at interface X. Note that the first-served manner. Routers are now called on to flows specified may or may not be mutually exclusive. For provide different qualities of service to different example, the first and second flow in Table 2 overlap. This is Uapplications, which means routers need new mechanisms common in practice, and when no explicit priorities are speci- such as admission control, resource reservation, per-flow fied, we follow the convention that rules closer to the top of queuing, and fair scheduling. All of these mechanisms the list take priority. require the router to distinguish packets belonging to differ- ent flows. Problem Statement Flows are specified by rules applied to incoming packets. Each rule of a classifier has d components. R[i] is the ith com- We call a collection of rules a classifier. Each rule specifies a ponent of rule R, and is a regular expression on the ith field flow to which a packet may belong based on some criteria of the packet header. A packet P is said to match rule R, if "i, applied to the packet header (shown in Fig. 1). To illustrate the ith field of the header of P, satisfies the regular expression the variety of classifiers, consider some examples of how pack- R[i]. In practice, a rule component is not a general regular et classification can be used by an Internet service provider expression but is often limited by syntax to a simple (ISP) to provide different services. Figure 2 shows ISP1 con- address/mask or operator/number(s) specification. In an nected to three different sites: enterprise networks E1 and E2, address/mask specification, a 0 (1) at bit position x in the and a network access point1 (NAP), which is in turn connect- mask denotes that the corresponding bit in the address is a ed to ISP2 and ISP3. ISP1 provides a number of different ser- don’t care (significant) bit. Examples of operator/number(s) vices to its customers, as shown in Table 1. specifications are eq 1232 and range 34-9339. Note that a pre- fix can be specified as an address/mask pair where the mask is contiguous (i.e., all bits with value 1 appear to the left of bits Service Example with value 0 in the mask). It can also be specified as a range of width equal to 2t where t = 32 – prefixlength. Most com- Packet filtering Deny all traffic from ISP3 (on interface X) destined to E2. 1 A network access point is a network site which acts as an exchange point for Policy routing Send all voice-over-IP traffic arriving from Internet traffic. ISPs connect to the NAP to exchange traffic with other ISPs. E1 (on interface Y) and destined to E2 via a separate ATM network. Flow Relevant packet fields Accounting and Treat all video traffic to E1 (via interface Y) as highest priority and perform accounting for the traffic sent this way. Email and from ISP2 Source link-layer address, source transport port number Traffic rate limiting Ensure that ISP2 does not inject more than 10 Mb/s of e-mail traffic and 50 Mb/s of From ISP2 Source link-layer address total traffic on interface X. From ISP3 and going Source link-layer address, Traffic shaping Ensure that no more than 50 Mb/s of Web to E2 destination network-layer address traffic is injected into ISP on interface X. 2 I Table 2. Flows into which an incoming packet must be classi- I Table 1. Customer services provided by ISP1. fied by the router at interface X. 24 0890-8044/01/$10.00 © 2001 IEEE IEEE Network • March/April 2001 L4-SP L4-DP L4-PROT L3-SA L3-DA L3-PROT L2-SA L2-DA Payload 16b 16b 8b 32b 32b 8b 48b 48b monly occurring specifications can be represented by ranges. An example real-life classifier in Transport layer header Network layer header Link layer header four dimensions is shown in Table 3. By convention, the first rule R1 is of L2: Layer 2 (e.g., Ethernet) DA: Destination address highest priority, and rule R7 is of low- L3: Layer 3 (e.g., IP) SA: Source address est priority. Some example classifica- L4: Layer 4 (e.g., TCP) PROT: Protocol tion results are shown in Table 4. SP: Source port DP: Destination port Longest prefix matching for routing lookups is a special case of one-dimen- I Figure 1. This figure shows some of the header fields (and their widths) that might be used sional packet classification. All packets for classifying the packet. Although not shown in this figure, higher-layer (e.g., application- destined to the set of addresses level) headers may also be used. described by a common prefix may be considered to be part of the same flow. The address of the next hop to which the packet should be forwarded is the associated action. The length of the Y E prefix defines the priority of the rule. 1 ISP1 Performance Metrics for Classification ISP2 Algorithms NAP X Z • Search speed — Faster links require faster classifica- ISP3 E tion. For example, links running at 10 Gb/s can Router 2 bring 31.25 million packets/s (assuming minimum- sized 40-byte TCP/IP packets). I Figure 2. An example network of an ISP (ISP ) connected to two enter- • Low storage requirements — Small storage require- 1 prise networks (E and E ) and to two other ISP networks across a net- ments enable the use of fast memory technologies 1 2 work access point (NAP). like static random access memory (SRAM). SRAM can be used as an on-chip cache by a software algo- rithm and as on-chip SRAM for a hardware algorithm. • Ability to handle large real-life classifiers. • Flexibility in specification — A classification algorithm should • Fast updates — As the classifier changes, the data struc- support general rules, including prefixes, operators (range, ture needs to be updated. We can categorize data struc- less than, greater than, equal to, etc.), and wildcards. In some tures into those which can add or delete entries applications, noncontiguous masks may be required. incrementally, and those which need to be reconstructed from scratch each time the classifier changes. When the Classification Algorithms data structure is reconstructed from scratch, we call it pre- processing. The update rate differs among different appli- Background cations: a very low update rate may be sufficient in For the next few sections, we will use the example classifier in firewalls where entries are added manually or infrequent- Table 5 repeatedly. The classifier has six rules in two fields ly, whereas a router with per-flow queues may require very labeled F1 and F2; each specification is a prefix of maximum frequent updates. length 3 bits. We will refer to the classifier as C = {Rj} and • Scalability in the number of header fields used for classification. each rule Rj as a 2-tuple: <Rjl, Rj2>. Rule Network-layer destination Network-layer source (address/ Transport-layer Transport-layer Action (address/mask) mask) destination protocol R1 152.163.190.69/255.255.255.255 152.163.80.11/255.255.255.255 * * Deny R2 152.168.3.0/255.255.255.0 152.163.200.157/255.255.255.255 eq www udp Deny R5 152.163.198.4/255.255.255.255 152.163.160.0/255.255.252.0 gt 1023 tcp Permit R6 0.0.0.0/0.0.0.0 0.0.0.0/0.0.0.0 * * Permit I Table 3. A real-life classifier in four dimensions. Packet Network-layer destination Network-layer source Transport-layer Transport-layer protocol Best matching rule, header destination action P1 152.163.190.69 152.163.80.11 www tcp R1, deny P2 152.168.3.21 152.163.200.157 www udp R2, deny P3 152.168.198.4 152.163.160.10 1024 tcp R5, permit I Table 4. Example classification results. IEEE Network • March/April 2001 25 111 P Definition 1 — Given a set of N disjoint ranges G = {Gi = [li, 110 W ui]} that form a partition of the number line [0,2 – 1], i.e., li and u are such that l = 0, l £ u , l = u + 1, u = 2W – 1; R5 R6 i 1 i i i+1 i N 101 the range lookup problem is to find the range GP (and any asso- ciated information) that contains an incoming point.
Recommended publications
  • Interval Trees Storing and Searching Intervals
    Interval Trees Storing and Searching Intervals • Instead of points, suppose you want to keep track of axis-aligned segments: • Range queries: return all segments that have any part of them inside the rectangle. • Motivation: wiring diagrams, genes on genomes Simpler Problem: 1-d intervals • Segments with at least one endpoint in the rectangle can be found by building a 2d range tree on the 2n endpoints. - Keep pointer from each endpoint stored in tree to the segments - Mark segments as you output them, so that you don’t output contained segments twice. • Segments with no endpoints in range are the harder part. - Consider just horizontal segments - They must cross a vertical side of the region - Leads to subproblem: Given a vertical line, find segments that it crosses. - (y-coords become irrelevant for this subproblem) Interval Trees query line interval Recursively build tree on interval set S as follows: Sort the 2n endpoints Let xmid be the median point Store intervals that cross xmid in node N intervals that are intervals that are completely to the completely to the left of xmid in Nleft right of xmid in Nright Another view of interval trees x Interval Trees, continued • Will be approximately balanced because by choosing the median, we split the set of end points up in half each time - Depth is O(log n) • Have to store xmid with each node • Uses O(n) storage - each interval stored once, plus - fewer than n nodes (each node contains at least one interval) • Can be built in O(n log n) time. • Can be searched in O(log n + k) time [k = #
    [Show full text]
  • Advanced Data Structures
    Advanced Data Structures PETER BRASS City College of New York CAMBRIDGE UNIVERSITY PRESS Cambridge, New York, Melbourne, Madrid, Cape Town, Singapore, São Paulo Cambridge University Press The Edinburgh Building, Cambridge CB2 8RU, UK Published in the United States of America by Cambridge University Press, New York www.cambridge.org Information on this title: www.cambridge.org/9780521880374 © Peter Brass 2008 This publication is in copyright. Subject to statutory exception and to the provision of relevant collective licensing agreements, no reproduction of any part may take place without the written permission of Cambridge University Press. First published in print format 2008 ISBN-13 978-0-511-43685-7 eBook (EBL) ISBN-13 978-0-521-88037-4 hardback Cambridge University Press has no responsibility for the persistence or accuracy of urls for external or third-party internet websites referred to in this publication, and does not guarantee that any content on such websites is, or will remain, accurate or appropriate. Contents Preface page xi 1 Elementary Structures 1 1.1 Stack 1 1.2 Queue 8 1.3 Double-Ended Queue 16 1.4 Dynamical Allocation of Nodes 16 1.5 Shadow Copies of Array-Based Structures 18 2 Search Trees 23 2.1 Two Models of Search Trees 23 2.2 General Properties and Transformations 26 2.3 Height of a Search Tree 29 2.4 Basic Find, Insert, and Delete 31 2.5ReturningfromLeaftoRoot35 2.6 Dealing with Nonunique Keys 37 2.7 Queries for the Keys in an Interval 38 2.8 Building Optimal Search Trees 40 2.9 Converting Trees into Lists 47 2.10
    [Show full text]
  • Search Trees
    Lecture III Page 1 “Trees are the earth’s endless effort to speak to the listening heaven.” – Rabindranath Tagore, Fireflies, 1928 Alice was walking beside the White Knight in Looking Glass Land. ”You are sad.” the Knight said in an anxious tone: ”let me sing you a song to comfort you.” ”Is it very long?” Alice asked, for she had heard a good deal of poetry that day. ”It’s long.” said the Knight, ”but it’s very, very beautiful. Everybody that hears me sing it - either it brings tears to their eyes, or else -” ”Or else what?” said Alice, for the Knight had made a sudden pause. ”Or else it doesn’t, you know. The name of the song is called ’Haddocks’ Eyes.’” ”Oh, that’s the name of the song, is it?” Alice said, trying to feel interested. ”No, you don’t understand,” the Knight said, looking a little vexed. ”That’s what the name is called. The name really is ’The Aged, Aged Man.’” ”Then I ought to have said ’That’s what the song is called’?” Alice corrected herself. ”No you oughtn’t: that’s another thing. The song is called ’Ways and Means’ but that’s only what it’s called, you know!” ”Well, what is the song then?” said Alice, who was by this time completely bewildered. ”I was coming to that,” the Knight said. ”The song really is ’A-sitting On a Gate’: and the tune’s my own invention.” So saying, he stopped his horse and let the reins fall on its neck: then slowly beating time with one hand, and with a faint smile lighting up his gentle, foolish face, he began..
    [Show full text]
  • 2 Dynamization
    6.851: Advanced Data Structures Spring 2010 Lecture 4 — February 11, 2010 Prof. Andr´eSchulz Scribe: Peter Caday 1 Overview In the previous lecture, we studied range trees and kd-trees, two structures which support efficient orthogonal range queries on a set of points. In this second of four lectures on geometric data structures, we will tie up a loose end from the last lecture — handling insertions and deletions. The main topic, however, will be two new structures addressing the vertical line stabbing problem: interval trees and segment trees. We will conclude with an application of vertical line stabbing to a windowing problem. 2 Dynamization In our previous discussion of range trees, we assumed that the point set was static. On the other hand, we may be interested in supporting insertions and deletions as time progresses. Unfortunately, it is not trivial to modify our data structures to handle this dynamic scenario. We can, however, dynamize them using general techniques; the techniques and their application here are due to Overmars [1]. Idea. Overmars’ dynamization is based on the idea of decomposable searches. A search (X,q) for the value q among the keys X is decomposable if the search result can be obtained in O(1) time from the results of searching (X1,q) and (X2,q), where X1 ∪ X2 = X. For instance, in the 2D kd-tree, the root node splits R2 into two halves. If we want to search for all points lying in a rectangle q, we may do this by combining the results of searching for q in each half.
    [Show full text]
  • Lecture Notes of CSCI5610 Advanced Data Structures
    Lecture Notes of CSCI5610 Advanced Data Structures Yufei Tao Department of Computer Science and Engineering Chinese University of Hong Kong July 17, 2020 Contents 1 Course Overview and Computation Models 4 2 The Binary Search Tree and the 2-3 Tree 7 2.1 The binary search tree . .7 2.2 The 2-3 tree . .9 2.3 Remarks . 13 3 Structures for Intervals 15 3.1 The interval tree . 15 3.2 The segment tree . 17 3.3 Remarks . 18 4 Structures for Points 20 4.1 The kd-tree . 20 4.2 A bootstrapping lemma . 22 4.3 The priority search tree . 24 4.4 The range tree . 27 4.5 Another range tree with better query time . 29 4.6 Pointer-machine structures . 30 4.7 Remarks . 31 5 Logarithmic Method and Global Rebuilding 33 5.1 Amortized update cost . 33 5.2 Decomposable problems . 34 5.3 The logarithmic method . 34 5.4 Fully dynamic kd-trees with global rebuilding . 37 5.5 Remarks . 39 6 Weight Balancing 41 6.1 BB[α]-trees . 41 6.2 Insertion . 42 6.3 Deletion . 42 6.4 Amortized analysis . 42 6.5 Dynamization with weight balancing . 43 6.6 Remarks . 44 1 CONTENTS 2 7 Partial Persistence 47 7.1 The potential method . 47 7.2 Partially persistent BST . 48 7.3 General pointer-machine structures . 52 7.4 Remarks . 52 8 Dynamic Perfect Hashing 54 8.1 Two random graph results . 54 8.2 Cuckoo hashing . 55 8.3 Analysis . 58 8.4 Remarks . 59 9 Binomial and Fibonacci Heaps 61 9.1 The binomial heap .
    [Show full text]
  • Buffer Trees
    Buffer Trees Lars Arge. The Buffer Tree: A New Technique for Optimal I/O Algorithms. In Proceedings of Fourth Workshop on Algorithms and Data Structures (WADS), Lecture Notes in Computer Science Vol. 955, Springer-Verlag, 1995, 334-345. 1 Computational Geometry 2 Pairwise Rectangle Intersection A Input N rectangles B D Output all R pairwise intersections F E Example (A; B) (B; C) (B; F ) (D; E) (D; F ) C Intersection Types Intersection Identified by: : : A B Orthogonal Line Segment Intersection on 4N rectangle sides D E Batched Range Searching on N rectangles and N upper-left corners Algorithm Orthogonal Line Segment Intersection + Batched Range Searching + Duplicate removal 3 Orthogonal Line Segment Intersection Input N segments, vertical and horizontal Output all R intersections Sweepline Algorithm Sort all endpoints w.r.t. x-coordinate • Sweep left-to-right with a range tree T y4 • storing the y-coordinates of horizontal segments intersecting the sweepline y3 Left endpoint insertion into T y • ) 2 Right endpoint deletion from T y • ) 1 Vertical segment [y ; y ] • 1 2 ) sweepline report T [y ; y ] \ 1 2 Total (internal) time O(N log N + R) · 2 4 Range Trees Create Create empty structure Insert(x) Insert element x Delete(x) Delete the inserted element x Report(x1; x2) Report all x [x1; x2] 2 x1 x2 Binary search trees B-trees (internal) (# I/Os) Updates O(log2 N) O(logB N) R Report O(log2 N + R) O(logB N + B ) Orthogonal Line Segment Intersection using B-trees O(Sort(N) + N log N + R ) I/Os : : : · B B 5 Batched Range Searching Input N rectangles and points Output all R (r; p) where point p is within rectangle r Sweepline Algorithm Sort all points and left/right rectangle • sides w.r.t.
    [Show full text]
  • Efficient Data Structures for Range Searching on a Grid MARK H
    JOURNAL OF ALGORITHMS 9,254-275 (1988) Efficient Data Structures for Range Searching on a Grid MARK H. OVERMARS Department of Computer Science, University of Utrecht, The Netherlands Received February 17,1987; accepted May 15.1987 We consider the 2-dimensional range searching problem in the case where all points lie on an integer grid. A new data structure is presented that solves range queries on a U * U grid in O( k + log log U) time using O( n log n) storage, where n is the number of points and k the number of reported answers. Although the query time is very good the preprocessing time of this method is very high. A second data structure is presented that can be built in time O( n log n) at the cost of an increase in query time to O(k + m). Similar techniques are used for solving the line segment intersection searching problem in a set of axis-parallel line segments on a grid. The methods presented also yield efficient structures for dominance searching and searching with half-infinite ranges that use only O(n) storage. A generalization to multi-dimensional space, using a normalization approach, yields a static solution to the general range searching problem that is better than any known solution when the dimension is at least 3. Q 1988 Academic Press, Inc. 1. INTRODUCTION One of the problems in computational geometry that has received a large amount of attention is the range searching problem. Given a set of n points in a d-dimensional space, the range searching problem asks to store these points such that for a given range ([A, * .
    [Show full text]
  • Lecture Range Searching II: Windowing Queries
    Computational Geometry · Lecture Range Searching II: Windowing Queries INSTITUT FUR¨ THEORETISCHE INFORMATIK · FAKULTAT¨ FUR¨ INFORMATIK Tamara Mchedlidze · Darren Strash 23.11.2015 1 Dr. Tamara Mchedlidze · Dr. Darren Strash · Computational Geometry Lecture Range Searching II Object types in range queries y0 y x x0 Setting so far: Input: set of points P (here P ⊂ R2) Output: all points in P \ [x; x0] × [y; y0] Data structures: kd-trees or range trees 2 Dr. Tamara Mchedlidze · Dr. Darren Strash · Computational Geometry Lecture Range Searching II Object types in range queries y0 y0 y x x0 y x x0 Setting so far: Further variant Input: set of points P Input: set of line segments S (here P ⊂ R2) (here in R2) Output: all points in Output: all segments in P \ [x; x0] × [y; y0] S \ [x; x0] × [y; y0] Data structures: kd-trees Data structures: ? or range trees 2 Dr. Tamara Mchedlidze · Dr. Darren Strash · Computational Geometry Lecture Range Searching II Axis-parallel line segments special case (e.g., in VLSI design): all line segments are axis-parallel 3 Dr. Tamara Mchedlidze · Dr. Darren Strash · Computational Geometry Lecture Range Searching II Axis-parallel line segments special case (e.g., in VLSI design): all line segments are axis-parallel Problem: Given n vertical and horizontal line segments and an axis-parallel rectangle R = [x; x0] × [y; y0], find all line segments that intersect R. 3 Dr. Tamara Mchedlidze · Dr. Darren Strash · Computational Geometry Lecture Range Searching II Axis-parallel line segments special case (e.g., in VLSI design): all line segments are axis-parallel Problem: Given n vertical and horizontal line segments and an axis-parallel rectangle R = [x; x0] × [y; y0], find all line segments that intersect R.
    [Show full text]
  • Segment Tree
    CS 5199 – Competition Programming and Problem Solving Seminar Segment Tree Raunak Kumar Based on slides by Paul Liu, Kuba Karpierz, Bruno Vacherot, Raunak Kumar and Jason Chiu for CPSC 490 – Problem Solving in Computer Science at The University of British Columbia 2019/10/07 Cornell University • Additionally, allow insertion/deletion of elements. • Solution: use a different data structure, like a binary search tree. We have a collection of elements and we would like to support some operations on these elements. ) Often, the solution is to use specialized data structures. Data Structures You are given an array A of n integers. We want to support the following operations • Print the array in sorted order. • Solution: Just sort the array and print it. 1 We have a collection of elements and we would like to support some operations on these elements. ) Often, the solution is to use specialized data structures. Data Structures You are given an array A of n integers. We want to support the following operations • Print the array in sorted order. • Solution: Just sort the array and print it. • Additionally, allow insertion/deletion of elements. • Solution: use a different data structure, like a binary search tree. 1 Data Structures You are given an array A of n integers. We want to support the following operations • Print the array in sorted order. • Solution: Just sort the array and print it. • Additionally, allow insertion/deletion of elements. • Solution: use a different data structure, like a binary search tree. We have a collection of elements and we would like to support some operations on these elements.
    [Show full text]
  • Multidimensional Segment Trees Can Do Range Updates in Poly-Logarithmic Time
    Multidimensional segment trees can do range updates in poly-logarithmic time Nabil Ibtehaz1, M. Kaykobad1, and M. Sohel Rahman1,* [email protected] , fkaykobad,[email protected] 1Department of CSE, BUET, ECE Building, West Palasi, Dhaka-1205, Bangladesh *Corresponding author December 8, 2020 Abstract Updating and querying on a range is a classical algorithmic problem with a multitude of applications. The Segment Tree data structure is particularly notable in handling the range query and update operations. A Segment Tree divides the range into disjoint segments and merges them together to perform range queries and range updates elegantly. Although this data structure is remarkably potent for 1- dimensional problems, it falls short in higher dimensions. Lazy Propagation enables the operations to be computed in O(logn) time in a single dimension. However, the concept of lazy propagation could not be translated to higher-dimensional cases, which imposes a time complexity of O(nk−1 logn) for operations on k-dimensional data. In this work, we have made an attempt to emulate the idea of lazy propagation differently so that it can be applied for 2-dimensional cases. Moreover, the proposed modification should be capable of performing most general aggregate functions similar to the original Segment Tree, and can also be extended to even higher dimensions. Our proposed algorithm manages to perform range sum queries and updates in O(log2 n) time for a 2-dimensional problem, which becomes O(logd n) for a d-dimensional situation. arXiv:1811.01226v2 [cs.DS] 6 Dec 2020 Index terms| Dynamic range query, Lazy Propagation, Multidimensional data, Range sum query, Segment Tree, Tree data structures 1 1 Introduction Range queries appear frequently in different problems in Computer Science.
    [Show full text]
  • Lecture 15: Windowing Queries
    Motivation Segment trees Windowing again Windowing queries Computational Geometry Lecture 15: Windowing queries Computational Geometry Lecture 15: Windowing queries Motivation Segment trees Windowing queries Windowing again Windowing Zoom in; re-center and zoom in; select by outlining Computational Geometry Lecture 15: Windowing queries Motivation Segment trees Windowing queries Windowing again Windowing Computational Geometry Lecture 15: Windowing queries Motivation Segment trees Windowing queries Windowing again Windowing Given a set of n axis-parallel line segments, preprocess them into a data structure so that the ones that intersect a query rectangle can be reported efficiently Computational Geometry Lecture 15: Windowing queries Motivation Segment trees Windowing queries Windowing again Windowing Given a set of n arbitrary, non-crossing line segments, preprocess them into a data structure so that the ones that intersect a query rectangle can be reported efficiently Computational Geometry Lecture 15: Windowing queries Motivation Segment trees Windowing queries Windowing again Windowing Two cases of intersection: An endpoint lies inside the query window; solve with range trees The segment intersects a side of the query window; solve how? Computational Geometry Lecture 15: Windowing queries Motivation Segment trees Windowing queries Windowing again Using a bounding box? If the query window intersects the line segment, then it also intersects the bounding box of the line segment (whose sides are axis-parallel segments) So we could search
    [Show full text]
  • Set Pruning Segment Trees for Packet Classification
    2011 International Conference on Advanced Information Networking and Applications Set Pruning Segment Trees for Packet Classification Yeim-Kuan Chang and Hsin-Mao Chen Department of Computer Science and Information Engineering, National Cheng Kung University, Tainan, Taiwan {ykchang, P76984500}@mail.ncku.edu.tw Abstract—Nowadays, multi-field packet classification is one of the dimensional classification. The key feature is to use pre- most important technologies to support various services in next computations to set switch pointers pointing to the part of data generation routers. In this paper, we propose a segment tree structure containing the matched rules. It is effective in dealing based parallel SRAM-based pipelined architecture called Set with prefixes, but it is not suitable for other fields such as port Pruning Segment Trees (SPST) for multi-dimensional packet ranges. To make Grid of Trie work for rules containing range classification. For solving the memory blowup problem, a fields, all the range field values must be converted to prefixes grouping scheme called Partition by Length (PL) is used to first. However, Prefixes are limited ranges and the size is a reduce the rule duplications in SPST. Additionally, we also power of two. In the worst case, a W-bit range needs to be propose an optimization called Set Pruning Multi-way Segment Trees (SPMST) to reduce the tree level and hardware cost. The converted to 2W – 2 prefixes. Thus, converting ranges to key feature of our proposed architecture is that memory prefixes becomes another source of suplications. HiCuts, consumption is reduced significantly regardless of the HyperCuts and DGST are suitable for range fields, but those characteristics of various rule tables.
    [Show full text]