Peter Novodvorsky <[EMAIL PROTECTED]> writes:
> So what can be done -- is to make some good interface in this
> library. It should generic enough for being applied to BSD ip stack
> too.
I don't think you understood what I wrote.
The details of what the Linux network stack expects from the rest
"Hi... teacher"
E-learning Company is starting . and we need your experience
This enterprise is an innovative company that operates in the "E_learning" field.
We can provide the opportunity to work independently, from your own home, whenever you
like,
teaching English to students all
Wolfgang Jährling <[EMAIL PROTECTED]> writes:
> It allocates an array of sys_nerr elements (the sys_nerr in glibc on
> GNU/Hurd is 119) and tries to store an object for each E* constant in
> one of those elements, but uses the actual value of the constant as
> offset. However, it doesn't crash wh
Most likely, YES !Here's why. Fierce ... take no prisoner ... insurance industry PRICE WARS have driven premiums DOWN, and down, and down --30 -- 40 -- 50 -- even 70% from where they were just a short time ago!YOUR INSURANCE COMPANY DOESN'T WANT YOU TO READ THIS...They will continue to take your m
Hi!
[ This message is about a general issue in GNU/Hurd, which i encountered
during i tried to fix Ruby, thus I think it's most relevant for this
list. ]
I tried to find out more about the problem with the E* constants in
Ruby. I found out that Ruby does the following:
It allocates an array
Hello, Jeroen!
> "Jeroen" == Jeroen Dekkers <[EMAIL PROTECTED]> writes:
Jeroen> On Sun, Jan 13, 2002 at 01:42:46AM +0300, Peter
Jeroen> Novodvorsky wrote:
>> I've read Protocol Service Decomposition for High-Performance
>> Networking and it influenced on me much. I think it r
Hi, Thomas!
> "Thomas" == Thomas Bushnell, BSG <[EMAIL PROTECTED]> writes:
Thomas> Peter Novodvorsky <[EMAIL PROTECTED]> writes:
>> 1). I propose to move all linux code out of pfinet and make
>> separated library with linux ip stack.
Thomas> This is not a horrible idea, and
Title: [µð¸ð¼Ç] °Á Ŀ¸®Å§·³ ¾È³»
µðÁöÅÐ ¿
On Sun, Jan 13, 2002 at 01:42:46AM +0300, Peter Novodvorsky wrote:
> I've read Protocol Service Decomposition for High-Performance
> Networking and it influenced on me much. I think it reasonable idea to
> insert a thin network interfaces code into kernel (actually what
> linux-src/net/core is). B
Peter Novodvorsky <[EMAIL PROTECTED]> writes:
> 1). I propose to move all linux code out of pfinet and make separated
> library with linux ip stack.
This is not a horrible idea, and I once thought of doing the same
thing myself.
However, two things block the idea:
1) The amount of Hurd speci
Hello!
I've read Protocol Service Decomposition for High-Performance
Networking and it influenced on me much. I think it reasonable idea to
insert a thin network interfaces code into kernel (actually what
linux-src/net/core is). But it is far goal and somebody might not
accept it.
One of ideas i
Title: JPMOLCA.COM
[ »ç»ó ÃÖ´ë À̺¥Æ® ]
2°³¿ù ÀÌ»ó °¡ÀÔÀÚ ¸ðµÎ »çÀºÇ° ÁõÁ¤.
±¹³»¿¡¼´Â ÃÖÃʽõµ ÀÚ·áµé
¸ðµç ±Ã±ÝÁõÀº ÃãÃß°í ÀÖ´Â ¿©ÀÎÀ» ´©¸£¸é ?
___
Bug-hurd mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-hurd
> I noticed that in gnumach/i386/i386/iopb.c, i386_io_port_add is careful
> to release all locks while running kalloc() to allocate some memory for
> the I/O bitmap, and goes back to retry via goto.
>
> Is this in general a good strategy? What is the danger that purposedly
> is avoided here? Do
Hi,
I noticed that in gnumach/i386/i386/iopb.c, i386_io_port_add is careful
to release all locks while running kalloc() to allocate some memory for
the I/O bitmap, and goes back to retry via goto.
Is this in general a good strategy? What is the danger that purposedly
is avoided here? Do I need
14 matches
Mail list logo
