Netdev List
 help / color / mirror / Atom feed
From: Luigi Rizzo <rizzo@iet.unipi.it>
To: netdev@vger.kernel.org
Subject: new version of netmap for linux (20120322)
Date: Thu, 22 Mar 2012 19:37:59 +0100	[thread overview]
Message-ID: <20120322183759.GA54931@onelab2.iet.unipi.it> (raw)
In-Reply-To: <20120312230809.GA45615@onelab2.iet.unipi.it>

I have updated the linux version of the netmap code,
specifically fixing the 'igb' driver which was not working earlier.

The code and tinycore images for today's version 20120322
are available in the same location

	http://info.iet.unipi.it/~luigi/netmap/

cheers
luigi

On Tue, Mar 13, 2012 at 12:08:09AM +0100, Luigi Rizzo wrote:
> just in case you might be interested...
> 
> i have recently completed a linux port of the netmap framework.
> Code, documentation and PicoBSD/Tinycore bootable images are at
> 
> 	http://info.iet.unipi.it/~luigi/netmap/
> 
> Netmap is a device-independent framework for packet generation and
> capture from user space; it can do line rate at 10Gbit/s (14.88Mpps)
> with just one core at about 1GHz.
> 
> Netmap relies on a kernel module (netmap_lin.ko) and slightly
> modified device drivers (about 4-500 lines per driver).  It requires
> no kernel patches apart from device drivers (and abusing the ax25
> field in struct netdevice).
> Userspace programs can use the native API (documented in netmap.4)
> or a libpcap emulation library. It has been integrated in FreeBSD
> last fall, and the linux version uses mostly the same code plus a bit
> of glue to adapt the BSD<->linux kernel ABI.
> 
> The current version supporting the ixgbe and e1000/e1000e driver.
> Patches for other devices (igb, r8169, forcedeth) are avaiable but
> untested.
> 
> 	cheers
> 	luigi

      reply	other threads:[~2012-03-22 18:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 23:08 netmap for linux now available Luigi Rizzo
2012-03-22 18:37 ` Luigi Rizzo [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120322183759.GA54931@onelab2.iet.unipi.it \
    --to=rizzo@iet.unipi.it \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox