qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@redhat.com>
To: Vincenzo Maffione <v.maffione@gmail.com>
Cc: marcel.a@redhat.com, jasowang@redhat.com, qemu-devel@nongnu.org,
	lcapitulino@redhat.com, aliguori@amazon.com, dmitry@daynix.com,
	pbonzini@redhat.com, g.lettieri@iet.unipi.it, rizzo@iet.unipi.it
Subject: Re: [Qemu-devel] [PATCH v3 3/5] net: TAP uses NetClientInfo offloading callbacks
Date: Thu, 6 Feb 2014 15:18:45 +0100	[thread overview]
Message-ID: <20140206141845.GA29457@stefanha-thinkpad.brq.redhat.com> (raw)
In-Reply-To: <1390237625-29304-4-git-send-email-v.maffione@gmail.com>

On Mon, Jan 20, 2014 at 06:07:03PM +0100, Vincenzo Maffione wrote:
> The TAP NetClientInfo structure is inizialized with the TAP-specific
> functions that manipulates offloading features.
> 
> Signed-off-by: Vincenzo Maffione <v.maffione@gmail.com>
> ---
>  net/tap.c | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> diff --git a/net/tap.c b/net/tap.c
> index c805f3c..d34ec88 100644
> --- a/net/tap.c
> +++ b/net/tap.c
> @@ -314,6 +314,12 @@ static NetClientInfo net_tap_info = {
>      .receive_iov = tap_receive_iov,
>      .poll = tap_poll,
>      .cleanup = tap_cleanup,
> +    .has_ufo = tap_has_ufo,
> +    .has_vnet_hdr = tap_has_vnet_hdr,
> +    .has_vnet_hdr_len = tap_has_vnet_hdr_len,
> +    .using_vnet_hdr = tap_using_vnet_hdr,
> +    .set_offload = tap_set_offload,
> +    .set_vnet_hdr_len = tap_set_vnet_hdr_len,
>  };
>  
>  static TAPState *net_tap_fd_init(NetClientState *peer,

Please make these tap_*() functions static.  They do not need to be
accessed from outside this source file.

I also noticed that you didn't touch tap-win32.c.  I guess it should
also assign its tap_has_ufo() and similar functions.  (tap-win32.c
declares its own net_tap_info struct.)  Here, we can also make the
functions static.

  reply	other threads:[~2014-02-06 14:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-20 17:07 [Qemu-devel] [PATCH v3 0/5] Add netmap backend offloadings support Vincenzo Maffione
2014-01-20 17:07 ` [Qemu-devel] [PATCH v3 1/5] net: change vnet-hdr TAP prototypes Vincenzo Maffione
2014-01-20 17:07 ` [Qemu-devel] [PATCH v3 2/5] net: extend NetClientInfo for offloading Vincenzo Maffione
2014-01-20 17:07 ` [Qemu-devel] [PATCH v3 3/5] net: TAP uses NetClientInfo offloading callbacks Vincenzo Maffione
2014-02-06 14:18   ` Stefan Hajnoczi [this message]
2014-02-06 14:23   ` Stefan Hajnoczi
2014-02-06 14:31     ` Vincenzo Maffione
2014-01-20 17:07 ` [Qemu-devel] [PATCH v3 4/5] net: virtio-net and vmxnet3 use offloading API Vincenzo Maffione
2014-01-20 17:07 ` [Qemu-devel] [PATCH v3 5/5] net: add offloading support to netmap backend Vincenzo Maffione
2014-02-06  9:30 ` [Qemu-devel] [PATCH v3 0/5] Add netmap backend offloadings support Vincenzo Maffione
2014-02-06 14:25 ` Stefan Hajnoczi

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=20140206141845.GA29457@stefanha-thinkpad.brq.redhat.com \
    --to=stefanha@redhat.com \
    --cc=aliguori@amazon.com \
    --cc=dmitry@daynix.com \
    --cc=g.lettieri@iet.unipi.it \
    --cc=jasowang@redhat.com \
    --cc=lcapitulino@redhat.com \
    --cc=marcel.a@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rizzo@iet.unipi.it \
    --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).