tle_ctx.h revision 9fa82a63
1/*
2 * Copyright (c) 2016  Intel Corporation.
3 * Licensed under the Apache License, Version 2.0 (the "License");
4 * you may not use this file except in compliance with the License.
5 * You may obtain a copy of the License at:
6 *
7 *     http://www.apache.org/licenses/LICENSE-2.0
8 *
9 * Unless required by applicable law or agreed to in writing, software
10 * distributed under the License is distributed on an "AS IS" BASIS,
11 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
12 * See the License for the specific language governing permissions and
13 * limitations under the License.
14 */
15
16#ifndef _TLE_CTX_H_
17#define _TLE_CTX_H_
18
19#include <stdint.h>
20#include <sys/socket.h>
21#include <netinet/in.h>
22#include <rte_common.h>
23#include <rte_mbuf.h>
24
25#ifdef __cplusplus
26extern "C" {
27#endif
28
29/**
30 * <tle_ctx>  - each such ctx represents an 'independent copy of the stack'.
31 * It owns set of <stream>s and <dev>s entities and provides
32 * (de)multiplexing input/output packets from/into devices into/from streams.
33 * <dev> is an abstraction for the underlying device, that is able
34 * to RX/TX packets and may provide some HW offload capabilities.
35 * It is a user responsibility to add to the <ctx> all <dev>s,
36 * that context has to manage, before starting to do stream operations
37 * (open/send/recv,close) over that context.
38 * Right now adding/deleting <dev>s to the context with open
39 * streams is not supported.
40 * <stream> represents an L4(UDP/TCP, etc.) endpoint <addr, port> and
41 * is an analogy to socket entity.
42 * As with a socket, there are ability to do recv/send over it.
43 * <stream> belongs to particular <ctx> but is visible globally across
44 * the process, i.e. any thread within the process can do recv/send over it
45 * without any further synchronisation.
46 * While 'upper' layer API is thread safe, lower layer API (rx_bulk/tx_bulk)
47 * is not thread safe and is not supposed to be run on multiple threads
48 * in parallel.
49 * So single thread can drive multiple <ctx>s and do IO for them,
50 * but multiple threads can't drive same <ctx> without some
51 * explicit synchronization.
52 */
53
54struct tle_ctx;
55struct tle_dev;
56
57/**
58 * Blocked L4 ports info.
59 */
60struct tle_bl_port {
61	uint32_t nb_port;     /**< number of blocked ports. */
62	const uint16_t *port; /**< list of blocked ports. */
63};
64
65
66/**
67 * device parameters.
68 */
69struct tle_dev_param {
70	uint32_t rx_offload; /**< DEV_RX_OFFLOAD_* supported. */
71	uint32_t tx_offload; /**< DEV_TX_OFFLOAD_* supported. */
72	struct in_addr local_addr4;  /**< local IPv4 address assigned. */
73	struct in6_addr local_addr6; /**< local IPv6 address assigned. */
74	struct tle_bl_port bl4; /**< blocked ports for IPv4 address. */
75	struct tle_bl_port bl6; /**< blocked ports for IPv4 address. */
76};
77
78#define TLE_DST_MAX_HDR	0x60
79
80struct tle_dest {
81	struct rte_mempool *head_mp;
82	/**< MP for fragment headers and control packets. */
83	struct tle_dev *dev;     /**< device to send packets through. */
84	uint16_t mtu;                /**< MTU for given destination. */
85	uint8_t l2_len;  /**< L2 header length. */
86	uint8_t l3_len;  /**< L3 header length. */
87	uint8_t hdr[TLE_DST_MAX_HDR]; /**< L2/L3 headers. */
88};
89
90/**
91 * context creation parameters.
92 */
93
94enum {
95	TLE_PROTO_UDP,
96	TLE_PROTO_TCP,
97	TLE_PROTO_NUM
98};
99
100enum {
101	TLE_JHASH,
102	TLE_SIPHASH,
103	TLE_HASH_NUM
104};
105
106struct tle_ctx_param {
107	int32_t socket_id;         /**< socket ID to allocate memory for. */
108	uint32_t proto;            /**< L4 proto to handle. */
109	uint32_t max_streams;      /**< max number of streams in context. */
110	uint32_t max_stream_rbufs; /**< max recv mbufs per stream. */
111	uint32_t max_stream_sbufs; /**< max send mbufs per stream. */
112	uint32_t send_bulk_size;   /**< expected # of packets per send call. */
113
114	int (*lookup4)(void *opaque, const struct in_addr *addr,
115		struct tle_dest *res);
116	/**< will be called by send() to get IPv4 packet destination info. */
117	void *lookup4_data;
118	/**< opaque data pointer for lookup4() callback. */
119
120	int (*lookup6)(void *opaque, const struct in6_addr *addr,
121		struct tle_dest *res);
122	/**< will be called by send() to get IPv6 packet destination info. */
123	void *lookup6_data;
124	/**< opaque data pointer for lookup6() callback. */
125
126	uint32_t hash_alg;
127	/**< hash algorithm to be used to generate sequence number. */
128	rte_xmm_t secret_key;
129	/**< secret key to be used to calculate the hash. */
130};
131
132/**
133 * create L4 processing context.
134 * @param ctx_prm
135 *   Parameters used to create and initialise the L4 context.
136 * @return
137 *   Pointer to context structure that can be used in future operations,
138 *   or NULL on error, with error code set in rte_errno.
139 *
140 *   Possible rte_errno errors include:
141 *   - EINVAL - invalid parameter passed to function
142 *   - ENOMEM - out of memory
143 */
144struct tle_ctx *
145tle_ctx_create(const struct tle_ctx_param *ctx_prm);
146
147/**
148 * Destroy given context.
149 *
150 * @param ctx
151 *   context to destroy
152 */
153void tle_ctx_destroy(struct tle_ctx *ctx);
154
155/**
156 * Add new device into the given context.
157 * This function is not multi-thread safe.
158 *
159 * @param ctx
160 *   context to add new device into.
161 * @param dev_prm
162 *   Parameters used to create and initialise new device inside the context.
163 * @return
164 *   Pointer to device structure that can be used in future operations,
165 *   or NULL on error, with error code set in rte_errno.
166 *   Possible rte_errno errors include:
167 *   - EINVAL - invalid parameter passed to function
168 *   - ENODEV - max possible value of open devices is reached
169 *   - ENOMEM - out of memory
170 */
171struct tle_dev *
172tle_add_dev(struct tle_ctx *ctx, const struct tle_dev_param *dev_prm);
173
174/**
175 * Remove and destroy previously added device from the given context.
176 * This function is not multi-thread safe.
177 *
178 * @param dev
179 *   device to remove and destroy.
180 * @return
181 *   zero on successful completion.
182 *   - -EINVAL - invalid parameter passed to function
183 */
184int tle_del_dev(struct tle_dev *dev);
185
186/**
187 * Flags to the context that destinations info might be changed,
188 * so if it has any destinations data cached, then
189 * it has to be invalidated.
190 * @param ctx
191 *   context to invalidate.
192 */
193void tle_ctx_invalidate(struct tle_ctx *ctx);
194
195/**
196 * Stream asynchronous notification mechanisms:
197 * a) recv/send callback.
198 * Stream recv/send notification callbacks behaviour is edge-triggered (ET).
199 * recv callback will be invoked if stream receive buffer was empty and
200 * new packet(s) have arrived.
201 * send callback will be invoked when stream send buffer was full,
202 * and some packets belonging to that stream were sent
203 * (part of send buffer became free again).
204 * Note that both recv and send callbacks are called with sort of read lock
205 * held on that stream. So it is not permitted to call stream_close()
206 * within the callback function. Doing that would cause a deadlock.
207 * While it is allowed to call stream send/recv functions within the
208 * callback, it is not recommended: callback function will be invoked
209 * within tle_udp_rx_bulk/tle_udp_tx_bulk context and some heavy processing
210 * within the callback functions might cause performance degradation
211 * or even loss of packets for further streams.
212 * b) recv/send event.
213 * Stream recv/send events behaviour is level-triggered (LT).
214 * receive event will be raised by either
215 * tle_udp_rx_burst() or tle_udp_stream_recv() as long as there are any
216 * remaining packets inside stream receive buffer.
217 * send event will be raised by either
218 * tle_udp_tx_burst() or tle_udp_stream_send() as long as there are any
219 * free space inside stream send buffer.
220 * Note that callback and event are mutually exclusive on <stream, op> basis.
221 * It is not possible to  open a stream with both recv event and callback
222 * specified.
223 * Though it is possible to open a stream with recv callback and send event,
224 * or visa-versa.
225 * If the user doesn't need any notification mechanism for that stream,
226 * both event and callback could be set to zero.
227 */
228
229struct tle_event;
230struct tle_stream;
231
232/**
233 * Stream recv/send callback function and data.
234 */
235struct tle_stream_cb {
236	void (*func)(void *, struct tle_stream *);
237	void *data;
238};
239
240#ifdef __cplusplus
241}
242#endif
243
244#endif /* _TLE_CTX_H_ */
245