All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Pirko <jiri@resnulli.us>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [net-next PATCH v2 5/6] i40e: Add TX and RX support in switchdev mode.
Date: Sat, 7 Jan 2017 09:27:47 +0100	[thread overview]
Message-ID: <20170107082747.GA2040@nanopsycho> (raw)
In-Reply-To: <20170106110858.1598bbb8@laptop>

Fri, Jan 06, 2017 at 08:08:58PM CET, kubakici at wp.pl wrote:
>On Fri, 6 Jan 2017 18:30:35 +0100, Jiri Pirko wrote:
>> >> > +	skb_dst_drop(skb);
>> >> > +	dst_hold(&priv->vfpr_dst->dst);
>> >> > +	skb_dst_set(skb, &priv->vfpr_dst->dst);
>> >> > +	skb->dev = vsi->netdev;  
>> >> This dst dance seems a bit odd to me. Why don't you just call
>> >> i40e_xmit_frame_ring with an extra arg holding the needed metadata?  
>> >
>> >We don't have TX/RX queues associated with VFPR netdevs, so we need to set
>> >the dev to PF netdev and requeue the skb.  
>> 
>> Still, you eventually call a function within same .c file. Using dst
>> does not look right to me.
>
>Do you mean you don't like reusing the dst_metadata to store the
>representative id?  The missing patch provided the reasoning behind
>this design [1].  It's mostly about being able to comfortably use the
>queuing infrastructure.  Trying to push data from multiple netdevs into
>single ring at driver layer is even less pretty.
>
>[1] http://patchwork.ozlabs.org/patch/710563/

Okay, makes sense. Thanks.


WARNING: multiple messages have this Message-ID (diff)
From: Jiri Pirko <jiri@resnulli.us>
To: Jakub Kicinski <kubakici@wp.pl>
Cc: "Samudrala, Sridhar" <sridhar.samudrala@intel.com>,
	alexander.h.duyck@intel.com, john.r.fastabend@intel.com,
	anjali.singhai@intel.com, jakub.kicinski@netronome.com,
	davem@davemloft.net, intel-wired-lan@lists.osuosl.org,
	netdev@vger.kernel.org
Subject: Re: [net-next PATCH v2 5/6] i40e: Add TX and RX support in switchdev mode.
Date: Sat, 7 Jan 2017 09:27:47 +0100	[thread overview]
Message-ID: <20170107082747.GA2040@nanopsycho> (raw)
In-Reply-To: <20170106110858.1598bbb8@laptop>

Fri, Jan 06, 2017 at 08:08:58PM CET, kubakici@wp.pl wrote:
>On Fri, 6 Jan 2017 18:30:35 +0100, Jiri Pirko wrote:
>> >> > +	skb_dst_drop(skb);
>> >> > +	dst_hold(&priv->vfpr_dst->dst);
>> >> > +	skb_dst_set(skb, &priv->vfpr_dst->dst);
>> >> > +	skb->dev = vsi->netdev;  
>> >> This dst dance seems a bit odd to me. Why don't you just call
>> >> i40e_xmit_frame_ring with an extra arg holding the needed metadata?  
>> >
>> >We don't have TX/RX queues associated with VFPR netdevs, so we need to set
>> >the dev to PF netdev and requeue the skb.  
>> 
>> Still, you eventually call a function within same .c file. Using dst
>> does not look right to me.
>
>Do you mean you don't like reusing the dst_metadata to store the
>representative id?  The missing patch provided the reasoning behind
>this design [1].  It's mostly about being able to comfortably use the
>queuing infrastructure.  Trying to push data from multiple netdevs into
>single ring at driver layer is even less pretty.
>
>[1] http://patchwork.ozlabs.org/patch/710563/

Okay, makes sense. Thanks.

  reply	other threads:[~2017-01-07  8:27 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-03 18:07 [Intel-wired-lan] [net-next PATCH v2 0/6] i40e: Add VF Port representator support for SR-IOV VFs Sridhar Samudrala
2017-01-03 18:07 ` Sridhar Samudrala
2017-01-03 18:07 ` [Intel-wired-lan] [net-next PATCH v2 1/6] i40e: Introduce devlink interface Sridhar Samudrala
2017-01-03 18:07   ` Sridhar Samudrala
2017-01-03 18:07 ` [Intel-wired-lan] [net-next PATCH v2 2/6] i40e: Introduce VF Port Representator(VFPR) netdevs Sridhar Samudrala
2017-01-03 18:07   ` Sridhar Samudrala
2017-01-05 12:44   ` [Intel-wired-lan] " Jiri Pirko
2017-01-05 12:44     ` Jiri Pirko
2017-01-05 21:46   ` [Intel-wired-lan] " Jeff Kirsher
2017-01-05 21:46     ` Jeff Kirsher
2017-01-06  0:42     ` Samudrala, Sridhar
2017-01-06  0:42       ` Samudrala, Sridhar
2017-01-03 18:07 ` [Intel-wired-lan] [net-next PATCH v2 3/6] i40e: Sync link state between VFs and VFPRs Sridhar Samudrala
2017-01-03 18:07   ` Sridhar Samudrala
2017-01-03 18:07 ` [Intel-wired-lan] [net-next PATCH v2 4/6] net: store port/representator id in metadata_dst Sridhar Samudrala
2017-01-03 18:07 ` [Intel-wired-lan] [net-next PATCH v2 5/6] i40e: Add TX and RX support in switchdev mode Sridhar Samudrala
2017-01-03 18:07   ` Sridhar Samudrala
2017-01-05 12:08   ` [Intel-wired-lan] " Or Gerlitz
2017-01-05 12:08     ` Or Gerlitz
2017-01-05 16:33     ` [Intel-wired-lan] " Jakub Kicinski
2017-01-05 16:33       ` Jakub Kicinski
2017-01-05 12:56   ` [Intel-wired-lan] " Jiri Pirko
2017-01-05 12:56     ` Jiri Pirko
2017-01-06  0:27     ` [Intel-wired-lan] " Samudrala, Sridhar
2017-01-06  0:27       ` Samudrala, Sridhar
2017-01-06 17:30       ` [Intel-wired-lan] " Jiri Pirko
2017-01-06 17:30         ` Jiri Pirko
2017-01-06 19:08         ` [Intel-wired-lan] " Jakub Kicinski
2017-01-06 19:08           ` Jakub Kicinski
2017-01-07  8:27           ` Jiri Pirko [this message]
2017-01-07  8:27             ` Jiri Pirko
2017-01-03 18:07 ` [Intel-wired-lan] [net-next PATCH v2 6/6] i40e: Add support for exposing VF port statistics via VFPR netdev on the host Sridhar Samudrala
2017-01-03 18:07   ` Sridhar Samudrala
2017-01-03 19:48 ` [Intel-wired-lan] [net-next PATCH v2 0/6] i40e: Add VF Port representator support for SR-IOV VFs Or Gerlitz
2017-01-03 19:48   ` Or Gerlitz
2017-01-03 20:04   ` [Intel-wired-lan] " Alexander Duyck
2017-01-03 20:04     ` Alexander Duyck
2017-01-03 20:24     ` Samudrala, Sridhar
2017-01-03 20:24       ` Samudrala, Sridhar
2017-01-03 20:45       ` Jakub Kicinski
2017-01-03 20:45         ` Jakub Kicinski

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=20170107082747.GA2040@nanopsycho \
    --to=jiri@resnulli.us \
    --cc=intel-wired-lan@osuosl.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 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.