overrun n.
1. [techspeak] Term for a frequent consequence
of data arriving faster than it can be consumed, esp. in serial
line communications. For example, at 9600 baud there is almost
exactly one character per millisecond, so if a silo can hold
only two characters and the machine takes longer than 2 msec to get
to service the interrupt, at least one character will be lost.
2. Also applied to non-serial-I/O communications. "I forgot to
pay my electric bill due to mail overrun." "Sorry, I got four
phone calls in 3 minutes last night and lost your message to
overrun." When thrashing at tasks, the next person to make a
request might be told "Overrun!" Compare firehose syndrome.
3. More loosely, may refer to a buffer overflow not
necessarily related to processing time (as in overrun screw).
1. [techspeak] Term for a frequent consequence
of data arriving faster than it can be consumed, esp. in serial
line communications. For example, at 9600 baud there is almost
exactly one character per millisecond, so if a silo can hold
only two characters and the machine takes longer than 2 msec to get
to service the interrupt, at least one character will be lost.
2. Also applied to non-serial-I/O communications. "I forgot to
pay my electric bill due to mail overrun." "Sorry, I got four
phone calls in 3 minutes last night and lost your message to
overrun." When thrashing at tasks, the next person to make a
request might be told "Overrun!" Compare firehose syndrome.
3. More loosely, may refer to a buffer overflow not
necessarily related to processing time (as in overrun screw).
Related:
- overrun: n. 1. [techspeak] Term for a frequent consequence of data
arriving faster than it can be consumed,
esp. in serial line communications. For example... - buffer overflow: n. What happens when you try to stuff more data
into a buffer (holding area) than it can handle.
This may be due to a mismatch in the processing... - buffer overflow n.
What happens when you try to stuff
more data into a buffer (holding area) than it can handle.
This problem is commonly exploited by crackers to... - spam vt.,vi.,n.
[from "Monty Python's Flying
Circus"] 1.
To crash a program by overrunning a fixed-size buffer... - firehose syndrome n.
In mainstream folklore it is observed
that trying to drink from a firehose can be a good way to rip your
lips off.
On computer networks, the absence or failure of flow... - firehose syndrome: n. In mainstream folklore it is observed that
trying to drink from a firehose can be a good way to rip your lips
off.
On computer networks, the absence or failure of flow... - bit bucket n.
[very common] 1. The universal data sink
(originally,
the mythical receptacle used to catch bits when they... - spam: [from the {MUD} community] vt. 1. To crash a program by
overrunning a fixed-size buffer with excessively large input data.
See also {buffer overflow}, {overrun screw}, {smash... - cycle
1. n. The basic unit of computation. What every
hacker wants more of (noted hacker Bill Gosper described himself as
a "cycle junkie").
One can describe an instruction as taking so many...
From the same category:
- indent style n.
[C, C++, and Java programmers] The rules
one uses to indent code in a readable fashion.
There are four major C indent styles, described... - die horribly v.
The software equivalent of crash and burn,
and the preferred emphatic form... - quotient n.
See coefficient of X... - nerd n.
1. [mainstream slang] Pejorative applied to anyone
with an above-average IQ and few gifts at small talk and ordinary
social rituals.
2. [jargon] Term of praise applied (in conscious... - Lions Book n.
"Source Code and Commentary on Unix
level 6",
by John Lions. The two parts of this book contained...
