aboutsummaryrefslogtreecommitdiffstats
path: root/extras/deprecated/dpdk-ipsec/dir.dox
blob: 05504541abb75cf7dcdad30823388d902986e9a8 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
/*
 * Copyright (c) 2016 Intel and/or its affiliates.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at:
 *
 *     http://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */

/* Doxygen directory documentation */

/**
@dir src/plugins/dpdk/ipsec
@brief IPSec ESP encrypt/decrypt using DPDK Cryptodev API.

This directory contains the source code for the DPDK Crypto abstraction layer.

*/
/*? %%clicmd:group_label DPDK Crypto %% ?*/
/*? %%syscfg:group_label DPDK Crypto %% ?*/
processing graph nodes in the vector, when the network processing represented by each graph node is applied to each packet in turn. Graph nodes are small and modular, and loosely coupled. This makes it easy to introduce new graph nodes and rewire existing graph nodes. Plugins are `shared libraries <https://en.wikipedia.org/wiki/Library_(computing)>`_ and are loaded at runtime by VPP. VPP find plugins by searching the plugin path for libraries, and then dynamically loads each one in turn on startup. A plugin can introduce new graph nodes or rearrange the packet processing graph. You can build a plugin completely independently of the FD.io VPP source tree, which means you can treat it as an independent component.