qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: qemu-devel@nongnu.org
Cc: Vincenzo Maffione <v.maffione@gmail.com>
Subject: [Qemu-devel] [PATCH 0/3] net: drop implicit peer from offload API
Date: Thu, 20 Feb 2014 12:14:06 +0100	[thread overview]
Message-ID: <1392894849-7907-1-git-send-email-stefanha@redhat.com> (raw)

This series is based on my net tree, which already has Vincenzo's "Add netmap
backend offloadings support" patch series merged.

After merging the series I realized we were bypassing the net.h API and
directly accessing nc->info->... in some cases.  This series cleans that up, at
the cost of moving ->peer back up to offload API callers.

I think that's the right thing to do to make net.h APIs consistent (the other
functions don't have implicit ->peer) and avoid bypassing the API.

Stefan Hajnoczi (3):
  net: remove implicit peer from offload API
  vhost_net: use offload API instead of bypassing it
  virtio-net: use qemu_get_queue() where possible

 hw/net/vhost_net.c  |  6 +++---
 hw/net/virtio-net.c | 12 ++++++------
 hw/net/vmxnet3.c    | 18 +++++++++---------
 include/net/net.h   | 14 +++++++-------
 net/net.c           | 36 ++++++++++++++++++------------------
 5 files changed, 43 insertions(+), 43 deletions(-)

-- 
1.8.5.3

             reply	other threads:[~2014-02-20 11:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 11:14 Stefan Hajnoczi [this message]
2014-02-20 11:14 ` [Qemu-devel] [PATCH 1/3] net: remove implicit peer from offload API Stefan Hajnoczi
2014-02-20 11:14 ` [Qemu-devel] [PATCH 2/3] vhost_net: use offload API instead of bypassing it Stefan Hajnoczi
2014-02-20 11:14 ` [Qemu-devel] [PATCH 3/3] virtio-net: use qemu_get_queue() where possible Stefan Hajnoczi
2014-02-20 11:58 ` [Qemu-devel] [PATCH 0/3] net: drop implicit peer from offload API 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=1392894849-7907-1-git-send-email-stefanha@redhat.com \
    --to=stefanha@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=v.maffione@gmail.com \
    /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).