Really, it sounds more like you want a custom driver that "owns" that
region of memory so it's marked as used and this driver is the gate
keeper. I wonder if the console frame buffer driver for the mips ip32
arch might be a good example for you as it swallows a several meg chunk of
memory fo
On Thu, 30 Aug 2007, Mohamed Bamakhrama wrote:
Hi all,
I have a question regarding the average number of assembly
instructions per line of kernel code. I know that this is a difficult
question since it depends on many factors such as the instruction set
Here's a quick answer, not the best, but
Just to throw my own observations into the war, I have to agree with David
K. here. This needs to be some sort of module and/or interface. Get the
policy into a replaceable user space module.
One of the hot areas for the kernel right now is for embedded systems.
They need an entirely different
Thanks Allen, you're exactly right. I'm charged with the task of finding
lots of nasties like that in our old code base where a number of things
were just hacked in down and dirty. Our embeded environment moved from
XINU on an SH2/SH3 with no mmu support and a BSD protocol stack we hacked
in ou
I've found the problem. This type of loop does not work:
do {
alarm(t);
read(fd);
if (EINT)
exception();
else
alarm(0);
} while (data);
There are some semantics here that differ from other *nix where this
works. The read() won't come out when the alarm comes, and
n the skb.
I would appreciate it if anyone more familiar with this code could point
me better to what I should be looking at, or at least explain what should
be happening that isn't.
TIA,
-S-
--
J. Scott Kasten
Email: jsk AT tetracon-eng DOT net
"In most cases, all an argument
6 matches
Mail list logo