All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vincenzo Maffione <v.maffione@gmail.com>
To: qemu-devel@nongnu.org
Cc: g.lettieri@iet.unipi.it, rizzo@iet.unipi.it, jasowang@redhat.com,
	Vincenzo Maffione <v.maffione@gmail.com>
Subject: [Qemu-devel] [PATCH 0/2] net: netmap: use nm_open() to open netmap port
Date: Fri,  8 Jan 2016 14:15:15 +0100	[thread overview]
Message-ID: <cover.1452258704.git.v.maffione@gmail.com> (raw)

Current implementation of netmap backend still uses the low level netmap
API to open, register and close netmap ports. However, the netmap_user.h
header provides some helper functions that make these tasks easier, with
the additional advantage of extended interface name semantic.

As an example, the extended semantic allows to open a netmap pipe over
a VALE port by specifying an interface name in the form "valeXX:YY{ZZ".
Other suffixes are used for netmap monitors, exclusive access, and to
specify special binding mode (e.g. single queue, RX-only, TX-only, etc.).
Details can be found in the netmap man page and in the netmap API headers.

Vincenzo Maffione (2):
  net: netmap: use nm_open() to open netmap ports
  net: netmap: avoid mmap() when ports use the same shared memory area

 net/netmap.c | 129 ++++++++++++++++++++++++++++++-----------------------------
 1 file changed, 66 insertions(+), 63 deletions(-)

-- 
2.7.0

             reply	other threads:[~2016-01-08 13:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-08 13:15 Vincenzo Maffione [this message]
2016-01-08 13:15 ` [Qemu-devel] [PATCH 1/2] net: netmap: use nm_open() to open netmap ports Vincenzo Maffione
2016-01-08 13:15 ` [Qemu-devel] [PATCH 2/2] net: netmap: avoid mmap() when ports use the same shared memory area Vincenzo Maffione
2016-01-14  3:25   ` Jason Wang
2016-01-22  8:35     ` Vincenzo Maffione

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=cover.1452258704.git.v.maffione@gmail.com \
    --to=v.maffione@gmail.com \
    --cc=g.lettieri@iet.unipi.it \
    --cc=jasowang@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rizzo@iet.unipi.it \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.