From: Kevin Bowling <kevin.bowling@kev009.com>
To: freebsd-net@freebsd.org
Cc: netdev@vger.kernel.org
Subject: Re: netmap, VALE and netmap pipes
Date: Mon, 17 Feb 2014 12:12:36 -0700 [thread overview]
Message-ID: <ldtmun$dqj$1@ger.gmane.org> (raw)
In-Reply-To: <CA+hQ2+gbs9aBneUaDGAnKVoPHspzc=5o+h+f_K=T+Cy8sRxr+w@mail.gmail.com>
On 2/17/2014 3:11 AM, Luigi Rizzo wrote:
> Hi,
> we have recently made a few extensions to netmap/VALE and put various
> pieces of code on public repositories, so i thought i'd share the
> pointers. All the code below runs with equal features and performance
> on FreeBSD and Linux, and we are trying to upstream it in the relevant
> projects if possible (as an example, QEMU recently added a netmap backend),
> at which point some of these clone repositories will become unnecessary.
Just a thought, maybe this is a good time for The FreeBSD Foundation to
reach out to The Linux Foundation for lobbying netmap into their main
line kernel. It would be nice if netmap becomes the de facto UNIX
standard for this type of programming (it is vendor neutral and broadly
applicable vs other solutions), and avoid not-invented-here APIs like
non-blocking I/O went through with all the UNIX flavors.
Regards,
Kevin Bowling
_______________________________________________
freebsd-net@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
next prev parent reply other threads:[~2014-02-17 19:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-17 10:11 netmap, VALE and netmap pipes Luigi Rizzo
2014-02-17 19:12 ` Kevin Bowling [this message]
2014-02-17 20:14 ` Stephen Hemminger
2014-02-17 20:33 ` Kevin Bowling
2014-02-22 1:03 ` jerry
2014-02-22 1:08 ` Luigi Rizzo
-- strict thread matches above, loose matches on Subject: below --
2014-02-17 10:15 Luigi Rizzo
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='ldtmun$dqj$1@ger.gmane.org' \
--to=kevin.bowling@kev009.com \
--cc=freebsd-net@freebsd.org \
--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;
as well as URLs for NNTP newsgroup(s).