svn commit: r232238 - in head: share/man/man4 sys/dev/e1000
sys/dev/ixgbe sys/dev/netmap sys/dev/re sys/net tools/tools/netmap
rizzo at iet.unipi.it
Wed Feb 29 09:33:13 UTC 2012
On Wed, Feb 29, 2012 at 01:14:33PM +0400, Slawa Olhovchenkov wrote:
> On Tue, Feb 28, 2012 at 10:58:56PM +0100, Luigi Rizzo wrote:
> > On Wed, Feb 29, 2012 at 12:35:23AM +0400, Slawa Olhovchenkov wrote:
> > ...
> > > > > > ?3. The two changes above unfortunately require an API change, so while
> > > > > > ? ? at it add a version field and some spares to the ioctl() argument
> > > > > > ? ? to help detect mismatches.
> > > > >
> > > > > Is it worth bumping __FreeBSD_version?
> > > >
> > > > I don't think it is necessary.
> > > > There is basically no code that uses the netmap API except for
> > > > the examples in tools/tools/netmap, and i now have a NETMAP_API macro
> > >
> > > no code in *FreeBSD base system*, yes?
> > > because I am write tools uses the netmap API now.
> > i am glad to hear that, and the NETMAP_API will serve you well
> > because you can use the same also on the Linux version of netmap
> Can you explain some detail about netmap?
> 1. What is order of send packets from different rings?
> 2. What is time packets sent? I am need sustain desired value of
> transfer rate.
Same as with the standard API:
1. it is the hardware that decides that. You can make no assumptions.
2. once again, once you have issued the system call,
it is the hardware that decides when it will send packets out.
More information about the svn-src-head