Home | History | Annotate | Download | only in doc

Lines Matching refs:user

34 \item To allow user to set traffic class bits.
36 \item To allow user to read traffic class bits of received packets.
42 \item To assign flow labels to packets sent by user.
149 message to user space, though the kernels which support flow labels
150 initialize it to zero. If user wants to get received flowinfo, he
224 storage, so that the full implementation necessarily includes user space flow
229 to user space. When user needs label he requests manager directly. The approach
233 One idea is to disallow not privileged user to allocate flow
239 \item {\bf ``Indirect''.} Kernel redirects requests to user level daemon
249 labels until their expiration and malicious user may fastly eat all the
289 to lease flow label ordered by user. In this case, it is user task to provide
316 #define IPV6_FL_S_USER 3 /* May be reused by this user */
320 \item \verb|linger| is time in seconds. After the last user releases flow
324 unprivileged user to set linger longer than 60 sec.
327 for this time, but it will not be destroyed before user released it explicitly
329 unprivileged user to set timeout longer than 60 sec. Proviledged applications
417 \verb|rtap| utility is modified to parse flow labels. F.e.\ if user allocated