netdev - RE: Fwd: Network Core

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <FCC0EC655BD1AE408C047268D1F5DF4C3BA60F08@NASANEXMB10.na.qualcomm.com>
Date:	Wed, 5 Nov 2008 12:46:30 -0800
From:	"Lovich, Vitali" <vlovich@...lcomm.com>
To:	Chris Snook <csnook@...hat.com>, "Diego ." <eljedi@...il.com>
CC:	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: Fwd: Network Core



> -----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