Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
P
PPSi
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
50
Issues
50
List
Board
Labels
Milestones
Merge Requests
1
Merge Requests
1
Wiki
Wiki
image/svg+xml
Discourse
Discourse
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Projects
PPSi
Commits
07ce9e52
Commit
07ce9e52
authored
Jul 21, 2014
by
Alessandro Rubini
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: documented drop support
Signed-off-by:
Alessandro Rubini
<
rubini@gnudd.com
>
parent
d16ddc1a
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
47 additions
and
2 deletions
+47
-2
ppsi-manual.in
doc/ppsi-manual.in
+47
-2
No files found.
doc/ppsi-manual.in
View file @
07ce9e52
...
@@ -35,7 +35,7 @@
...
@@ -35,7 +35,7 @@
@setchapternewpage off
@setchapternewpage off
@set update-month
March
2014
@set update-month
July
2014
@set release
__
RELEASE
_
GIT
_
ID
__
@set release
__
RELEASE
_
GIT
_
ID
__
@finalout
@finalout
...
@@ -427,11 +427,56 @@ may document the keywords, if the time allows it.
...
@@ -427,11 +427,56 @@ may document the keywords, if the time allows it.
configuration options. This applies to the priorities, intervals and
configuration options. This applies to the priorities, intervals and
thresholds, as well as the @i
{
slave-only
}
flag.
thresholds, as well as the @i
{
slave-only
}
flag.
@c ==========================================================================
@node Configuring Faults
@section Configuring Faults
Configuration, for @t
{
arch-unix
}
and @t
{
arch-wrs
}
, allows to provide
some fault injection.
In particular, the program allows dropping frames, in both the TX and RX
paths. The configuration values state how many frames are dropped every
1000. Dropping is randomized, but the user can set the seed to ensure
a repeatable dropping sequence.
Dropping transmitted frames is performed by reporting success (and the
timestamp), while no frame is actually sent. A diagnostic message
is generated at @t
{
frames
}
level 1, but other than than that nothing
happens. Actually, @t
{
arch-wrs
}
needs to actually send a frame in
order to get a timestamp back; in this case the program modifies the
frame, to use a wrong Ethernet type or a wrong UDP port.
Dropping received frames is performed by actually receiving (and
timestamping), but returning a special error code to the caller.
Again, PPSi creates a diagnostic message at @t
{
frames
}
level 1.
The following configuration lines are supported:
@table @code
@item rx-drop <value>
@itemx tx-drop <value>
Drop @i
{
value
}
frames every 1000 frames received or sent.
The randomized sequence is global.
@end table
The randomization see can be passed by pre-setting the environment
variable @t
{
PPSI
_
DROP
_
SEED
}
to a decimal numeric value. For example:
@smallexample
export PPSI
_
DROP
_
SEED=33
@end smallexample
@noindent
before starting the daemon.
@c ==========================================================================
@c ==========================================================================
@node Configuring the Simulator
@node Configuring the Simulator
@section Configuring the Simulator
@section Configuring the Simulator
To
t
un the PPSi simulator you need to rely on diagnostics and specific
To
r
un the PPSi simulator you need to rely on diagnostics and specific
configuration items. The configuration items are defined in
configuration items. The configuration items are defined in
@i
{
arch-sim/sim-conf.c
}
and are not individually documented here at
@i
{
arch-sim/sim-conf.c
}
and are not individually documented here at
this point.
this point.
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment