[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <530d01580811051503t74edc554g384373256f67c91@mail.gmail.com>
Date: Thu, 6 Nov 2008 00:03:48 +0100
From: "Diego ." <eljedi@...il.com>
To: "Lovich, Vitali" <vlovich@...lcomm.com>
Cc: "Chris Snook" <csnook@...hat.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: Fwd: Network Core
wow men!
thank all of you for the answears. Very usefull information..
thanks once again!!
On Wed, Nov 5, 2008 at 9:46 PM, Lovich, Vitali <vlovich@...lcomm.com> wrote:
>
>
>> -----Original Message-----
>> From: netdev-owner@...r.kernel.org [mailto:netdev-
>> owner@...r.kernel.org] On Behalf Of Chris Snook
>> Sent: November-05-08 12:12 PM
>> To: Diego .
>> Cc: netdev@...r.kernel.org
>> Subject: Re: Fwd: Network Core
>>
>> Diego . wrote:
>> There are a few O'Reilly books about the kernel networking stack, and
>> anything
>> written in the past few years should be recent enough for your
>> purposes. It
>> would probably also be helpful to read articles (such as those on
>> lwn.net) about
>> new network stack features that have been added. The commentary there
>> will give
>> you a general idea of the challenges you'll face, but you'll need to
>> complement
>> that with experience working with the network code.
>>
>> -- Chris
> Another idea, at least perhaps from a starting point is to determine whether or not it actually needs to be in user space. With the addition of the tx ring buffer to af_packet, it should be possible to experiment with your network stack in user space. Once you're comfortable and feel confident with the stack itself, you can port it to kernel space eventually if you want to.
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists