Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
/*
|
2012-02-13 18:56:34 +00:00
|
|
|
* Copyright (C) 2011-2012 Matteo Landi, Luigi Rizzo. All rights reserved.
|
2012-10-19 04:13:12 +00:00
|
|
|
*
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
* Redistribution and use in source and binary forms, with or without
|
|
|
|
* modification, are permitted provided that the following conditions
|
|
|
|
* are met:
|
1. Fix the handling of link reset while in netmap more.
A link reset now is completely transparent for the netmap client:
even if the NIC resets its own ring (e.g. restarting from 0),
the client will not see any change in the current rx/tx positions,
because the driver will keep track of the offset between the two.
2. make the device-specific code more uniform across different drivers
There were some inconsistencies in the implementation of the netmap
support routines, now drivers have been aligned to a common
code structure.
3. import netmap support for ixgbe . This is implemented as a very
small patch for ixgbe.c (233 lines, 11 chunks, mostly comments:
in total the patch has only 54 lines of new code) , as most of
the code is in an external file sys/dev/netmap/ixgbe_netmap.h ,
following some initial comments from Jack Vogel about making
changes less intrusive.
(Note, i have emailed Jack multiple times asking if he had
comments on this structure of the code; i got no reply so
i assume he is fine with it).
Support for other drivers (em, lem, re, igb) will come later.
"ixgbe" is now the reference driver for netmap support. Both the
external file (sys/dev/netmap/ixgbe_netmap.h) and the device-specific
patches (in sys/dev/ixgbe/ixgbe.c) are heavily commented and should
serve as a reference for other device drivers.
Tested on i386 and amd64 with the pkt-gen program in tools/tools/netmap,
the sender does 14.88 Mpps at 1050 Mhz and 14.2 Mpps at 900 MHz
on an i7-860 with 4 cores and 82599 card. Haven't tried yet more
aggressive optimizations such as adding 'prefetch' instructions
in the time-critical parts of the code.
2011-12-05 12:06:53 +00:00
|
|
|
* 1. Redistributions of source code must retain the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer.
|
|
|
|
* 2. Redistributions in binary form must reproduce the above copyright
|
|
|
|
* notice, this list of conditions and the following disclaimer in the
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
* documentation and/or other materials provided with the distribution.
|
2012-10-19 04:13:12 +00:00
|
|
|
*
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
|
|
|
|
* ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
|
|
* IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
|
|
* ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
|
|
|
|
* FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
|
|
* DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
|
|
* OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
|
|
* HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
|
|
* LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
|
|
* OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
|
|
* SUCH DAMAGE.
|
|
|
|
*/
|
|
|
|
|
|
|
|
/*
|
|
|
|
* $FreeBSD$
|
2012-10-19 04:13:12 +00:00
|
|
|
* $Id: netmap_kern.h 11829 2012-09-26 04:06:34Z luigi $
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
*
|
|
|
|
* The header contains the definitions of constants and function
|
|
|
|
* prototypes used only in kernelspace.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#ifndef _NET_NETMAP_KERN_H_
|
|
|
|
#define _NET_NETMAP_KERN_H_
|
|
|
|
|
2012-04-13 16:03:07 +00:00
|
|
|
#define NETMAP_MEM2 // use the new memory allocator
|
|
|
|
|
2012-02-13 18:56:34 +00:00
|
|
|
#if defined(__FreeBSD__)
|
2012-07-26 16:45:28 +00:00
|
|
|
#define likely(x) __builtin_expect(!!(x), 1)
|
|
|
|
#define unlikely(x) __builtin_expect(!!(x), 0)
|
|
|
|
|
2012-02-13 18:56:34 +00:00
|
|
|
#define NM_LOCK_T struct mtx
|
|
|
|
#define NM_SELINFO_T struct selinfo
|
|
|
|
#define MBUF_LEN(m) ((m)->m_pkthdr.len)
|
|
|
|
#define NM_SEND_UP(ifp, m) ((ifp)->if_input)(ifp, m)
|
2012-02-27 19:05:01 +00:00
|
|
|
#elif defined (linux)
|
2012-02-13 18:56:34 +00:00
|
|
|
#define NM_LOCK_T spinlock_t
|
|
|
|
#define NM_SELINFO_T wait_queue_head_t
|
|
|
|
#define MBUF_LEN(m) ((m)->len)
|
|
|
|
#define NM_SEND_UP(ifp, m) netif_rx(m)
|
2012-07-26 16:45:28 +00:00
|
|
|
|
|
|
|
#ifndef DEV_NETMAP
|
|
|
|
#define DEV_NETMAP
|
|
|
|
#endif
|
|
|
|
|
|
|
|
/*
|
2012-10-19 04:13:12 +00:00
|
|
|
* IFCAP_NETMAP goes into net_device's priv_flags (if_capenable).
|
|
|
|
* This was 16 bits up to linux 2.6.36, so we need a 16 bit value on older
|
2012-07-26 16:45:28 +00:00
|
|
|
* platforms and tolerate the clash with IFF_DYNAMIC and IFF_BRIDGE_PORT.
|
2012-10-19 04:13:12 +00:00
|
|
|
* For the 32-bit value, 0x100000 has no clashes until at least 3.5.1
|
2012-07-26 16:45:28 +00:00
|
|
|
*/
|
|
|
|
#if LINUX_VERSION_CODE < KERNEL_VERSION(2,6,37)
|
2012-07-27 10:31:26 +00:00
|
|
|
#define IFCAP_NETMAP 0x8000
|
2012-07-26 16:45:28 +00:00
|
|
|
#else
|
2012-07-27 10:31:26 +00:00
|
|
|
#define IFCAP_NETMAP 0x100000
|
2012-07-26 16:45:28 +00:00
|
|
|
#endif
|
|
|
|
|
|
|
|
#elif defined (__APPLE__)
|
2012-10-19 04:13:12 +00:00
|
|
|
#warning apple support is incomplete.
|
2012-07-26 16:45:28 +00:00
|
|
|
#define likely(x) __builtin_expect(!!(x), 1)
|
|
|
|
#define unlikely(x) __builtin_expect(!!(x), 0)
|
|
|
|
#define NM_LOCK_T IOLock *
|
|
|
|
#define NM_SELINFO_T struct selinfo
|
|
|
|
#define MBUF_LEN(m) ((m)->m_pkthdr.len)
|
|
|
|
#define NM_SEND_UP(ifp, m) ((ifp)->if_input)(ifp, m)
|
|
|
|
|
2012-02-13 18:56:34 +00:00
|
|
|
#else
|
|
|
|
#error unsupported platform
|
|
|
|
#endif
|
|
|
|
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
#define ND(format, ...)
|
2012-01-13 11:58:06 +00:00
|
|
|
#define D(format, ...) \
|
|
|
|
do { \
|
|
|
|
struct timeval __xxts; \
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
microtime(&__xxts); \
|
2012-01-13 11:58:06 +00:00
|
|
|
printf("%03d.%06d %s [%d] " format "\n", \
|
|
|
|
(int)__xxts.tv_sec % 1000, (int)__xxts.tv_usec, \
|
|
|
|
__FUNCTION__, __LINE__, ##__VA_ARGS__); \
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
} while (0)
|
2012-10-19 04:13:12 +00:00
|
|
|
|
|
|
|
/* rate limited, lps indicates how many per second */
|
|
|
|
#define RD(lps, format, ...) \
|
|
|
|
do { \
|
|
|
|
static int t0, __cnt; \
|
|
|
|
if (t0 != time_second) { \
|
|
|
|
t0 = time_second; \
|
|
|
|
__cnt = 0; \
|
|
|
|
} \
|
|
|
|
if (__cnt++ < lps) \
|
|
|
|
D(format, ##__VA_ARGS__); \
|
|
|
|
} while (0)
|
|
|
|
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
struct netmap_adapter;
|
|
|
|
|
|
|
|
/*
|
2012-02-27 19:05:01 +00:00
|
|
|
* private, kernel view of a ring. Keeps track of the status of
|
|
|
|
* a ring across system calls.
|
|
|
|
*
|
|
|
|
* nr_hwcur index of the next buffer to refill.
|
|
|
|
* It corresponds to ring->cur - ring->reserved
|
|
|
|
*
|
|
|
|
* nr_hwavail the number of slots "owned" by userspace.
|
|
|
|
* nr_hwavail =:= ring->avail + ring->reserved
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
*
|
2012-02-13 18:56:34 +00:00
|
|
|
* The indexes in the NIC and netmap rings are offset by nkr_hwofs slots.
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
* This is so that, on a reset, buffers owned by userspace are not
|
|
|
|
* modified by the kernel. In particular:
|
2012-02-13 18:56:34 +00:00
|
|
|
* RX rings: the next empty buffer (hwcur + hwavail + hwofs) coincides with
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
* the next empty buffer as known by the hardware (next_to_check or so).
|
|
|
|
* TX rings: hwcur + hwofs coincides with next_to_send
|
2013-01-17 22:14:58 +00:00
|
|
|
*
|
|
|
|
* For received packets, slot->flags is set to nkr_slot_flags
|
|
|
|
* so we can provide a proper initial value (e.g. set NS_FORWARD
|
|
|
|
* when operating in 'transparent' mode).
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
*/
|
|
|
|
struct netmap_kring {
|
|
|
|
struct netmap_ring *ring;
|
|
|
|
u_int nr_hwcur;
|
|
|
|
int nr_hwavail;
|
2012-01-26 09:55:16 +00:00
|
|
|
u_int nr_kflags; /* private driver flags */
|
2012-04-12 11:27:09 +00:00
|
|
|
#define NKR_PENDINTR 0x1 // Pending interrupt.
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
u_int nkr_num_slots;
|
|
|
|
|
2013-01-17 22:14:58 +00:00
|
|
|
uint16_t nkr_slot_flags; /* initial value for flags */
|
1. Fix the handling of link reset while in netmap more.
A link reset now is completely transparent for the netmap client:
even if the NIC resets its own ring (e.g. restarting from 0),
the client will not see any change in the current rx/tx positions,
because the driver will keep track of the offset between the two.
2. make the device-specific code more uniform across different drivers
There were some inconsistencies in the implementation of the netmap
support routines, now drivers have been aligned to a common
code structure.
3. import netmap support for ixgbe . This is implemented as a very
small patch for ixgbe.c (233 lines, 11 chunks, mostly comments:
in total the patch has only 54 lines of new code) , as most of
the code is in an external file sys/dev/netmap/ixgbe_netmap.h ,
following some initial comments from Jack Vogel about making
changes less intrusive.
(Note, i have emailed Jack multiple times asking if he had
comments on this structure of the code; i got no reply so
i assume he is fine with it).
Support for other drivers (em, lem, re, igb) will come later.
"ixgbe" is now the reference driver for netmap support. Both the
external file (sys/dev/netmap/ixgbe_netmap.h) and the device-specific
patches (in sys/dev/ixgbe/ixgbe.c) are heavily commented and should
serve as a reference for other device drivers.
Tested on i386 and amd64 with the pkt-gen program in tools/tools/netmap,
the sender does 14.88 Mpps at 1050 Mhz and 14.2 Mpps at 900 MHz
on an i7-860 with 4 cores and 82599 card. Haven't tried yet more
aggressive optimizations such as adding 'prefetch' instructions
in the time-critical parts of the code.
2011-12-05 12:06:53 +00:00
|
|
|
int nkr_hwofs; /* offset between NIC and netmap ring */
|
2012-02-13 18:56:34 +00:00
|
|
|
struct netmap_adapter *na;
|
|
|
|
NM_SELINFO_T si; /* poll/select wait queue */
|
|
|
|
NM_LOCK_T q_lock; /* used if no device lock available */
|
2012-01-26 09:55:16 +00:00
|
|
|
} __attribute__((__aligned__(64)));
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
|
|
|
|
/*
|
2012-02-13 18:56:34 +00:00
|
|
|
* This struct extends the 'struct adapter' (or
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
* equivalent) device descriptor. It contains all fields needed to
|
|
|
|
* support netmap operation.
|
|
|
|
*/
|
|
|
|
struct netmap_adapter {
|
2012-10-19 04:13:12 +00:00
|
|
|
/*
|
|
|
|
* On linux we do not have a good way to tell if an interface
|
|
|
|
* is netmap-capable. So we use the following trick:
|
|
|
|
* NA(ifp) points here, and the first entry (which hopefully
|
|
|
|
* always exists and is at least 32 bits) contains a magic
|
|
|
|
* value which we can use to detect that the interface is good.
|
|
|
|
*/
|
|
|
|
uint32_t magic;
|
|
|
|
uint32_t na_flags; /* future place for IFCAP_NETMAP */
|
|
|
|
#define NAF_SKIP_INTR 1 /* use the regular interrupt handler.
|
|
|
|
* useful during initialization
|
|
|
|
*/
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
int refcount; /* number of user-space descriptors using this
|
|
|
|
interface, which is equal to the number of
|
|
|
|
struct netmap_if objs in the mapped region. */
|
2012-04-13 16:03:07 +00:00
|
|
|
/*
|
|
|
|
* The selwakeup in the interrupt thread can use per-ring
|
|
|
|
* and/or global wait queues. We track how many clients
|
|
|
|
* of each type we have so we can optimize the drivers,
|
|
|
|
* and especially avoid huge contention on the locks.
|
|
|
|
*/
|
|
|
|
int na_single; /* threads attached to a single hw queue */
|
|
|
|
int na_multi; /* threads attached to multiple hw queues */
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
|
|
|
|
int separate_locks; /* set if the interface suports different
|
|
|
|
locks for rx, tx and core. */
|
|
|
|
|
2012-08-08 15:27:01 +00:00
|
|
|
u_int num_rx_rings; /* number of adapter receive rings */
|
|
|
|
u_int num_tx_rings; /* number of adapter transmit rings */
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
|
|
|
|
u_int num_tx_desc; /* number of descriptor in each queue */
|
|
|
|
u_int num_rx_desc;
|
|
|
|
|
|
|
|
/* tx_rings and rx_rings are private but allocated
|
|
|
|
* as a contiguous chunk of memory. Each array has
|
|
|
|
* N+1 entries, for the adapter queues and for the host queue.
|
|
|
|
*/
|
|
|
|
struct netmap_kring *tx_rings; /* array of TX rings. */
|
|
|
|
struct netmap_kring *rx_rings; /* array of RX rings. */
|
|
|
|
|
2012-02-27 19:05:01 +00:00
|
|
|
NM_SELINFO_T tx_si, rx_si; /* global wait queues */
|
|
|
|
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
/* copy of if_qflush and if_transmit pointers, to intercept
|
|
|
|
* packets from the network stack when netmap is active.
|
|
|
|
*/
|
|
|
|
int (*if_transmit)(struct ifnet *, struct mbuf *);
|
|
|
|
|
|
|
|
/* references to the ifnet and device routines, used by
|
|
|
|
* the generic netmap functions.
|
|
|
|
*/
|
|
|
|
struct ifnet *ifp; /* adapter is ifp->if_softc */
|
|
|
|
|
2012-02-13 18:56:34 +00:00
|
|
|
NM_LOCK_T core_lock; /* used if no device lock available */
|
|
|
|
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
int (*nm_register)(struct ifnet *, int onoff);
|
2012-02-13 18:56:34 +00:00
|
|
|
void (*nm_lock)(struct ifnet *, int what, u_int ringid);
|
|
|
|
int (*nm_txsync)(struct ifnet *, u_int ring, int lock);
|
|
|
|
int (*nm_rxsync)(struct ifnet *, u_int ring, int lock);
|
2013-01-23 03:51:47 +00:00
|
|
|
/* return configuration information */
|
|
|
|
int (*nm_config)(struct ifnet *, u_int *txr, u_int *txd,
|
|
|
|
u_int *rxr, u_int *rxd);
|
2012-07-26 16:45:28 +00:00
|
|
|
|
|
|
|
int bdg_port;
|
2012-02-27 19:05:01 +00:00
|
|
|
#ifdef linux
|
|
|
|
struct net_device_ops nm_ndo;
|
2012-07-26 16:45:28 +00:00
|
|
|
int if_refcount; // XXX additions for bridge
|
2012-02-27 19:05:01 +00:00
|
|
|
#endif /* linux */
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
2012-10-19 04:13:12 +00:00
|
|
|
* The combination of "enable" (ifp->if_capenable & IFCAP_NETMAP)
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
* and refcount gives the status of the interface, namely:
|
|
|
|
*
|
|
|
|
* enable refcount Status
|
|
|
|
*
|
|
|
|
* FALSE 0 normal operation
|
|
|
|
* FALSE != 0 -- (impossible)
|
|
|
|
* TRUE 1 netmap mode
|
|
|
|
* TRUE 0 being deleted.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#define NETMAP_DELETING(_na) ( ((_na)->refcount == 0) && \
|
|
|
|
( (_na)->ifp->if_capenable & IFCAP_NETMAP) )
|
|
|
|
|
|
|
|
/*
|
|
|
|
* parameters for (*nm_lock)(adapter, what, index)
|
|
|
|
*/
|
|
|
|
enum {
|
|
|
|
NETMAP_NO_LOCK = 0,
|
|
|
|
NETMAP_CORE_LOCK, NETMAP_CORE_UNLOCK,
|
|
|
|
NETMAP_TX_LOCK, NETMAP_TX_UNLOCK,
|
|
|
|
NETMAP_RX_LOCK, NETMAP_RX_UNLOCK,
|
2012-02-13 18:56:34 +00:00
|
|
|
#ifdef __FreeBSD__
|
|
|
|
#define NETMAP_REG_LOCK NETMAP_CORE_LOCK
|
|
|
|
#define NETMAP_REG_UNLOCK NETMAP_CORE_UNLOCK
|
|
|
|
#else
|
|
|
|
NETMAP_REG_LOCK, NETMAP_REG_UNLOCK
|
|
|
|
#endif
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
|
|
|
* The following are support routines used by individual drivers to
|
|
|
|
* support netmap operation.
|
|
|
|
*
|
|
|
|
* netmap_attach() initializes a struct netmap_adapter, allocating the
|
|
|
|
* struct netmap_ring's and the struct selinfo.
|
|
|
|
*
|
|
|
|
* netmap_detach() frees the memory allocated by netmap_attach().
|
|
|
|
*
|
|
|
|
* netmap_start() replaces the if_transmit routine of the interface,
|
|
|
|
* and is used to intercept packets coming from the stack.
|
|
|
|
*
|
|
|
|
* netmap_load_map/netmap_reload_map are helper routines to set/reset
|
|
|
|
* the dmamap for a packet buffer
|
|
|
|
*
|
|
|
|
* netmap_reset() is a helper routine to be called in the driver
|
|
|
|
* when reinitializing a ring.
|
|
|
|
*/
|
|
|
|
int netmap_attach(struct netmap_adapter *, int);
|
|
|
|
void netmap_detach(struct ifnet *);
|
|
|
|
int netmap_start(struct ifnet *, struct mbuf *);
|
|
|
|
enum txrx { NR_RX = 0, NR_TX = 1 };
|
|
|
|
struct netmap_slot *netmap_reset(struct netmap_adapter *na,
|
|
|
|
enum txrx tx, int n, u_int new_cur);
|
|
|
|
int netmap_ring_reinit(struct netmap_kring *);
|
|
|
|
|
2012-08-02 11:59:43 +00:00
|
|
|
extern u_int netmap_buf_size;
|
2012-04-12 11:27:09 +00:00
|
|
|
#define NETMAP_BUF_SIZE netmap_buf_size
|
2012-01-26 09:55:16 +00:00
|
|
|
extern int netmap_mitigate;
|
2012-02-08 11:43:29 +00:00
|
|
|
extern int netmap_no_pendintr;
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
extern u_int netmap_total_buffers;
|
|
|
|
extern char *netmap_buffer_base;
|
|
|
|
extern int netmap_verbose; // XXX debugging
|
|
|
|
enum { /* verbose flags */
|
|
|
|
NM_VERB_ON = 1, /* generic verbose */
|
|
|
|
NM_VERB_HOST = 0x2, /* verbose host stack */
|
|
|
|
NM_VERB_RXSYNC = 0x10, /* verbose on rxsync/txsync */
|
|
|
|
NM_VERB_TXSYNC = 0x20,
|
|
|
|
NM_VERB_RXINTR = 0x100, /* verbose on rx/tx intr (driver) */
|
|
|
|
NM_VERB_TXINTR = 0x200,
|
|
|
|
NM_VERB_NIC_RXSYNC = 0x1000, /* verbose on rx/tx intr (driver) */
|
|
|
|
NM_VERB_NIC_TXSYNC = 0x2000,
|
|
|
|
};
|
|
|
|
|
|
|
|
/*
|
2011-12-23 16:03:57 +00:00
|
|
|
* NA returns a pointer to the struct netmap adapter from the ifp,
|
|
|
|
* WNA is used to write it.
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
*/
|
2011-12-23 16:03:57 +00:00
|
|
|
#ifndef WNA
|
|
|
|
#define WNA(_ifp) (_ifp)->if_pspare[0]
|
|
|
|
#endif
|
|
|
|
#define NA(_ifp) ((struct netmap_adapter *)WNA(_ifp))
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
|
2012-10-19 04:13:12 +00:00
|
|
|
/*
|
|
|
|
* Macros to determine if an interface is netmap capable or netmap enabled.
|
|
|
|
* See the magic field in struct netmap_adapter.
|
|
|
|
*/
|
|
|
|
#ifdef __FreeBSD__
|
|
|
|
/*
|
|
|
|
* on FreeBSD just use if_capabilities and if_capenable.
|
|
|
|
*/
|
|
|
|
#define NETMAP_CAPABLE(ifp) (NA(ifp) && \
|
|
|
|
(ifp)->if_capabilities & IFCAP_NETMAP )
|
|
|
|
|
|
|
|
#define NETMAP_SET_CAPABLE(ifp) \
|
|
|
|
(ifp)->if_capabilities |= IFCAP_NETMAP
|
|
|
|
|
|
|
|
#else /* linux */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* on linux:
|
|
|
|
* we check if NA(ifp) is set and its first element has a related
|
|
|
|
* magic value. The capenable is within the struct netmap_adapter.
|
|
|
|
*/
|
|
|
|
#define NETMAP_MAGIC 0x52697a7a
|
|
|
|
|
|
|
|
#define NETMAP_CAPABLE(ifp) (NA(ifp) && \
|
|
|
|
((uint32_t)(uintptr_t)NA(ifp) ^ NA(ifp)->magic) == NETMAP_MAGIC )
|
|
|
|
|
|
|
|
#define NETMAP_SET_CAPABLE(ifp) \
|
|
|
|
NA(ifp)->magic = ((uint32_t)(uintptr_t)NA(ifp)) ^ NETMAP_MAGIC
|
|
|
|
|
|
|
|
#endif /* linux */
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
|
2012-07-26 16:45:28 +00:00
|
|
|
#ifdef __FreeBSD__
|
2012-01-13 10:21:15 +00:00
|
|
|
/* Callback invoked by the dma machinery after a successfull dmamap_load */
|
|
|
|
static void netmap_dmamap_cb(__unused void *arg,
|
2012-01-13 11:58:06 +00:00
|
|
|
__unused bus_dma_segment_t * segs, __unused int nseg, __unused int error)
|
2012-01-13 10:21:15 +00:00
|
|
|
{
|
|
|
|
}
|
|
|
|
|
|
|
|
/* bus_dmamap_load wrapper: call aforementioned function if map != NULL.
|
|
|
|
* XXX can we do it without a callback ?
|
|
|
|
*/
|
|
|
|
static inline void
|
|
|
|
netmap_load_map(bus_dma_tag_t tag, bus_dmamap_t map, void *buf)
|
|
|
|
{
|
|
|
|
if (map)
|
|
|
|
bus_dmamap_load(tag, map, buf, NETMAP_BUF_SIZE,
|
2012-01-13 11:58:06 +00:00
|
|
|
netmap_dmamap_cb, NULL, BUS_DMA_NOWAIT);
|
2012-01-13 10:21:15 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
/* update the map when a buffer changes. */
|
|
|
|
static inline void
|
|
|
|
netmap_reload_map(bus_dma_tag_t tag, bus_dmamap_t map, void *buf)
|
|
|
|
{
|
|
|
|
if (map) {
|
|
|
|
bus_dmamap_unload(tag, map);
|
|
|
|
bus_dmamap_load(tag, map, buf, NETMAP_BUF_SIZE,
|
2012-01-13 11:58:06 +00:00
|
|
|
netmap_dmamap_cb, NULL, BUS_DMA_NOWAIT);
|
2012-01-13 10:21:15 +00:00
|
|
|
}
|
|
|
|
}
|
2012-07-26 16:45:28 +00:00
|
|
|
#else /* linux */
|
|
|
|
|
|
|
|
/*
|
|
|
|
* XXX How do we redefine these functions:
|
|
|
|
*
|
|
|
|
* on linux we need
|
2012-07-27 10:31:26 +00:00
|
|
|
* dma_map_single(&pdev->dev, virt_addr, len, direction)
|
|
|
|
* dma_unmap_single(&adapter->pdev->dev, phys_addr, len, direction
|
2012-07-26 16:45:28 +00:00
|
|
|
* The len can be implicit (on netmap it is NETMAP_BUF_SIZE)
|
|
|
|
* unfortunately the direction is not, so we need to change
|
|
|
|
* something to have a cross API
|
|
|
|
*/
|
|
|
|
#define netmap_load_map(_t, _m, _b)
|
|
|
|
#define netmap_reload_map(_t, _m, _b)
|
|
|
|
#if 0
|
|
|
|
struct e1000_buffer *buffer_info = &tx_ring->buffer_info[l];
|
|
|
|
/* set time_stamp *before* dma to help avoid a possible race */
|
|
|
|
buffer_info->time_stamp = jiffies;
|
|
|
|
buffer_info->mapped_as_page = false;
|
|
|
|
buffer_info->length = len;
|
|
|
|
//buffer_info->next_to_watch = l;
|
|
|
|
/* reload dma map */
|
|
|
|
dma_unmap_single(&adapter->pdev->dev, buffer_info->dma,
|
2012-07-27 10:31:26 +00:00
|
|
|
NETMAP_BUF_SIZE, DMA_TO_DEVICE);
|
2012-07-26 16:45:28 +00:00
|
|
|
buffer_info->dma = dma_map_single(&adapter->pdev->dev,
|
2012-07-27 10:31:26 +00:00
|
|
|
addr, NETMAP_BUF_SIZE, DMA_TO_DEVICE);
|
2012-07-26 16:45:28 +00:00
|
|
|
|
|
|
|
if (dma_mapping_error(&adapter->pdev->dev, buffer_info->dma)) {
|
|
|
|
D("dma mapping error");
|
|
|
|
/* goto dma_error; See e1000_put_txbuf() */
|
|
|
|
/* XXX reset */
|
|
|
|
}
|
|
|
|
tx_desc->buffer_addr = htole64(buffer_info->dma); //XXX
|
|
|
|
|
|
|
|
#endif
|
|
|
|
|
|
|
|
/*
|
|
|
|
* The bus_dmamap_sync() can be one of wmb() or rmb() depending on direction.
|
|
|
|
*/
|
|
|
|
#define bus_dmamap_sync(_a, _b, _c)
|
|
|
|
|
|
|
|
#endif /* linux */
|
2012-01-13 10:21:15 +00:00
|
|
|
|
2012-02-15 23:13:29 +00:00
|
|
|
/*
|
|
|
|
* functions to map NIC to KRING indexes (n2k) and vice versa (k2n)
|
|
|
|
*/
|
|
|
|
static inline int
|
2012-02-27 19:05:01 +00:00
|
|
|
netmap_idx_n2k(struct netmap_kring *kr, int idx)
|
2012-02-15 23:13:29 +00:00
|
|
|
{
|
2012-02-27 19:05:01 +00:00
|
|
|
int n = kr->nkr_num_slots;
|
|
|
|
idx += kr->nkr_hwofs;
|
|
|
|
if (idx < 0)
|
|
|
|
return idx + n;
|
|
|
|
else if (idx < n)
|
|
|
|
return idx;
|
2012-02-15 23:13:29 +00:00
|
|
|
else
|
2012-02-27 19:05:01 +00:00
|
|
|
return idx - n;
|
2012-02-15 23:13:29 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
|
|
|
static inline int
|
2012-02-27 19:05:01 +00:00
|
|
|
netmap_idx_k2n(struct netmap_kring *kr, int idx)
|
2012-02-15 23:13:29 +00:00
|
|
|
{
|
2012-02-27 19:05:01 +00:00
|
|
|
int n = kr->nkr_num_slots;
|
|
|
|
idx -= kr->nkr_hwofs;
|
|
|
|
if (idx < 0)
|
|
|
|
return idx + n;
|
|
|
|
else if (idx < n)
|
|
|
|
return idx;
|
2012-02-15 23:13:29 +00:00
|
|
|
else
|
2012-02-27 19:05:01 +00:00
|
|
|
return idx - n;
|
2012-02-15 23:13:29 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
|
2012-04-13 16:03:07 +00:00
|
|
|
#ifdef NETMAP_MEM2
|
|
|
|
/* Entries of the look-up table. */
|
|
|
|
struct lut_entry {
|
|
|
|
void *vaddr; /* virtual address. */
|
|
|
|
vm_paddr_t paddr; /* phisical address. */
|
|
|
|
};
|
|
|
|
|
|
|
|
struct netmap_obj_pool;
|
|
|
|
extern struct lut_entry *netmap_buffer_lut;
|
|
|
|
#define NMB_VA(i) (netmap_buffer_lut[i].vaddr)
|
|
|
|
#define NMB_PA(i) (netmap_buffer_lut[i].paddr)
|
|
|
|
#else /* NETMAP_MEM1 */
|
|
|
|
#define NMB_VA(i) (netmap_buffer_base + (i * NETMAP_BUF_SIZE) )
|
|
|
|
#endif /* NETMAP_MEM2 */
|
|
|
|
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
/*
|
2012-01-10 19:57:23 +00:00
|
|
|
* NMB return the virtual address of a buffer (buffer 0 on bad index)
|
|
|
|
* PNMB also fills the physical address
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
*/
|
2012-01-10 19:57:23 +00:00
|
|
|
static inline void *
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
NMB(struct netmap_slot *slot)
|
|
|
|
{
|
|
|
|
uint32_t i = slot->buf_idx;
|
2012-07-26 16:45:28 +00:00
|
|
|
return (unlikely(i >= netmap_total_buffers)) ? NMB_VA(0) : NMB_VA(i);
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
}
|
|
|
|
|
2012-01-10 19:57:23 +00:00
|
|
|
static inline void *
|
|
|
|
PNMB(struct netmap_slot *slot, uint64_t *pp)
|
|
|
|
{
|
|
|
|
uint32_t i = slot->buf_idx;
|
2012-04-13 16:03:07 +00:00
|
|
|
void *ret = (i >= netmap_total_buffers) ? NMB_VA(0) : NMB_VA(i);
|
|
|
|
#ifdef NETMAP_MEM2
|
|
|
|
*pp = (i >= netmap_total_buffers) ? NMB_PA(0) : NMB_PA(i);
|
|
|
|
#else
|
2012-01-10 19:57:23 +00:00
|
|
|
*pp = vtophys(ret);
|
2012-04-13 16:03:07 +00:00
|
|
|
#endif
|
2012-01-10 19:57:23 +00:00
|
|
|
return ret;
|
|
|
|
}
|
|
|
|
|
2012-02-13 18:56:34 +00:00
|
|
|
/* default functions to handle rx/tx interrupts */
|
|
|
|
int netmap_rx_irq(struct ifnet *, int, int *);
|
|
|
|
#define netmap_tx_irq(_n, _q) netmap_rx_irq(_n, _q, NULL)
|
2012-07-26 16:45:28 +00:00
|
|
|
|
|
|
|
extern int netmap_copy;
|
Bring in support for netmap, a framework for very efficient packet
I/O from userspace, capable of line rate at 10G, see
http://info.iet.unipi.it/~luigi/netmap/
At this time I am bringing in only the generic code (sys/dev/netmap/
plus two headers under sys/net/), and some sample applications in
tools/tools/netmap. There is also a manpage in share/man/man4 [1]
In order to make use of the framework you need to build a kernel
with "device netmap", and patch individual drivers with the code
that you can find in
sys/dev/netmap/head.diff
The file will go away as the relevant pieces are committed to
the various device drivers, which should happen in a few days
after talking to the driver maintainers.
Netmap support is available at the moment for Intel 10G and 1G
cards (ixgbe, em/lem/igb), and for the Realtek 1G card ("re").
I have partial patches for "bge" and am starting to work on "cxgbe".
Hopefully changes are trivial enough so interested third parties
can submit their patches. Interested people can contact me
for advice on how to add netmap support to specific devices.
CREDITS:
Netmap has been developed by Luigi Rizzo and other collaborators
at the Universita` di Pisa, and supported by EU project CHANGE
(http://www.change-project.eu/)
The code is distributed under a BSD Copyright.
[1] In my opinion is a bad idea to have all manpage in one directory.
We should place kernel documentation in the same dir that contains
the code, which would make it much simpler to keep doc and code
in sync, reduce the clutter in share/man/ and incidentally is
the policy used for all of userspace code.
Makefiles and doc tools can be trivially adjusted to find the
manpages in the relevant subdirs.
2011-11-17 12:17:39 +00:00
|
|
|
#endif /* _NET_NETMAP_KERN_H_ */
|