netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vlad Yasevich <vyasevic@redhat.com>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, stephen@redhat.com,
	bridge@lists.linux-foundation.org, shmulik.ladkani@gmail.com,
	mst@redhat.com
Subject: Re: [PATCH net-next v5 01/14] vlan: wrap hw-acceleration calls in separate functions.
Date: Thu, 10 Jan 2013 20:08:27 -0500	[thread overview]
Message-ID: <50EF660B.2090500@redhat.com> (raw)
In-Reply-To: <20130110140749.153023fa@nehalam.linuxnetplumber.net>

On 01/10/2013 05:07 PM, Stephen Hemminger wrote:
> On Thu, 10 Jan 2013 13:41:58 -0500
> Vlad Yasevich <vyasevic@redhat.com> wrote:
>
>> On 01/10/2013 01:25 PM, Stephen Hemminger wrote:
>>> On Wed,  9 Jan 2013 12:17:48 -0500
>>> Vlad Yasevich <vyasevic@redhat.com> wrote:
>>>
>>>>
>>>>    /**
>>>> + * vlan_hw_buggy - Check to see if VLAN hw acceleration is supported.
>>>> + * @dev: netdevice of the lowerdev/hw nic
>>>> + *
>>>> + * Checks to see if HW and driver report VLAN acceleration correctly.
>>>> + */
>>>> +static inline bool vlan_hw_buggy(const struct net_device *dev)
>>>> +{
>>>> +	const struct net_device_ops *ops = dev->netdev_ops;
>>>> +
>>>> +	if ((dev->features & NETIF_F_HW_VLAN_FILTER) &&
>>>> +	    (!ops->ndo_vlan_rx_add_vid || !ops->ndo_vlan_rx_kill_vid))
>>>> +		return true;
>>>> +
>>>> +	return false;
>>>> +}
>>>> +
>>>> +/**
>>>> + * vlan_vid_add_hw - Add the VLAN vid to the HW filter
>>>> + * @dev: netdevice of the lowerdev/hw nic
>>>> + * @vid: vlan id.
>>>> + *
>>>> + * Inserts the vid into the HW vlan filter table if hw supports it.
>>>> + */
>>>> +static inline int vlan_vid_add_hw(struct net_device *dev,
>>>> +				  unsigned short vid)
>>>> +{
>>>> +	const struct net_device_ops *ops = dev->netdev_ops;
>>>> +	int err = 0;
>>>> +
>>>> +	if ((dev->features & NETIF_F_HW_VLAN_FILTER) &&
>>>> +	    ops->ndo_vlan_rx_add_vid)
>>>> +		err = ops->ndo_vlan_rx_add_vid(dev, vid);
>>>> +
>>>> +	return err;
>>>> +}
>>>> +
>>>> +/**
>>>> + * vlan_vid_del_hw - Delete the VLAN vid from the HW filter
>>>> + * @dev: netdevice of the lowerdev/hw nic
>>>> + * @vid: vlan id.
>>>> + *
>>>> + * Delete the vid from the HW vlan filter table if hw supports it.
>>>> + */
>>>> +static inline int vlan_vid_del_hw(struct net_device *dev,
>>>> +				  unsigned short vid)
>>>> +{
>>>> +	const struct net_device_ops *ops = dev->netdev_ops;
>>>> +	int err = 0;
>>>> +
>>>> +	if ((dev->features & NETIF_F_HW_VLAN_FILTER) &&
>>>> +	    ops->ndo_vlan_rx_kill_vid)
>>>> +		err = ops->ndo_vlan_rx_add_vid(dev, vid);
>>>> +
>>>> +	return err;
>>>> +}
>>>> +
>>>
>>> I would rather not have all these inline's. This isn't performance critical.
>>
>> I kind of need to keep them as inlines because of the VLAN support is
>> built.  Right now, none of the VLAN files are build if VLAN support is
>> turned off.  So all we get access to are inlines from if_vlan.h.
>>
>> I suppose I can change how VLANs get built, but not if that's the right
>> thing.  It looks like it is set up the way it is on purpose.
>>
>>> Also, the check for buggy devices should be done inside the vlan code,
>>> not repeated in the functions using the add/remove API. When device is
>>> registered the flag and add/kill should be checked, and if the device driver
>>> is buggy it should fail the register_netdevice.
>>>
>>
>> Not sure what you mean here.  I don't check if it's buggy again.  I
>> check that the device supports filter and the pointer is set.  I does
>> exactly what the code used to do.  I suppose that the checks for valid
>> function pointers may be a little redundant since otherwise
>> vlan_hw_buggy() would have triggered, but it's safer to have them since
>> we can't guarantee that other users have checked for buggy implementations.
>>
>> -vlad
>
> The best way to handle this is to add stubs for the unconfigure case, and
> include real code if configured.
>
> I.e something like
>
> #if IS_ENABLED(CONFIG_VLAN_8012Q)
> extern int vlan_vid_add_hw(struct net_device *, unsigned short);
> extern int vlan_vid_del_hw(struct net_device *, unsigned short);
> #else
> #define vlan_vid_add_hw(dev,vid) (-ENOTSUPP)
> #define vlan_vid_del_hw(dev,vid) (-ENOTSUPP)
> #endif
>
>

But that wouldn't be right as this would prevent HW filtering from
working when VLAN support isn't built in which defeats the whole point
of extracting this code out it its own functions so it can be re-used.

Either we always build in some parts of VLAN support or we make keep 
these inlines.

-vlad

>

  reply	other threads:[~2013-01-11  1:08 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-09 17:17 [PATCH net-next V5 00/14] Add basic VLAN support to bridges Vlad Yasevich
2013-01-09 17:17 ` [PATCH net-next v5 01/14] vlan: wrap hw-acceleration calls in separate functions Vlad Yasevich
2013-01-10 18:25   ` Stephen Hemminger
2013-01-10 18:41     ` Vlad Yasevich
2013-01-10 22:07       ` Stephen Hemminger
2013-01-11  1:08         ` Vlad Yasevich [this message]
2013-01-11 17:20           ` Stephen Hemminger
2013-01-11 17:41             ` Vlad Yasevich
2013-01-11 18:23               ` Stephen Hemminger
2013-01-11 18:53                 ` Vlad Yasevich
2013-01-09 17:17 ` [PATCH net-next v5 02/14] bridge: Add vlan filtering infrastructure Vlad Yasevich
2013-01-10 18:36   ` Stephen Hemminger
2013-01-10 19:01     ` Vlad Yasevich
2013-01-10 19:23       ` Vlad Yasevich
2013-01-10 22:10         ` Stephen Hemminger
2013-01-11  1:14           ` Vlad Yasevich
2013-01-11 13:53             ` Shmulik Ladkani
2013-01-11 15:33               ` Vlad Yasevich
2013-01-09 17:17 ` [PATCH net-next v5 03/14] bridge: Validate that vlan is permitted on ingress Vlad Yasevich
2013-01-09 17:17 ` [PATCH net-next v5 04/14] bridge: Verify that a vlan is allowed to egress on give port Vlad Yasevich
2013-01-09 17:17 ` [PATCH net-next v5 05/14] bridge: Cache vlan in the cb for faster egress lookup Vlad Yasevich
2013-01-09 17:17 ` [PATCH net-next v5 06/14] bridge: Add vlan to unicast fdb entries Vlad Yasevich
2013-01-09 17:17 ` [PATCH net-next v5 07/14] bridge: Add vlan id to multicast groups Vlad Yasevich
2013-01-09 17:17 ` [PATCH net-next v5 08/14] bridge: Add netlink interface to configure vlans on bridge ports Vlad Yasevich
2013-01-09 17:17 ` [PATCH net-next v5 09/14] bridge: Add vlan support to static neighbors Vlad Yasevich
2013-01-09 17:17 ` [PATCH net-next v5 10/14] bridge: Add the ability to configure pvid Vlad Yasevich
2013-01-09 17:17 ` [PATCH 10/14] bridge: Add the ability to pvid Vlad Yasevich
2013-01-09 17:24   ` Vlad Yasevich
2013-01-09 17:17 ` [PATCH net-next v5 11/14] bridge: API to configure egress policy Vlad Yasevich
2013-01-09 17:18 ` [PATCH net-next v5 12/14] bridge: Implement vlan ingress/egress policy Vlad Yasevich
2013-01-09 17:18 ` [PATCH net-next v5 13/14] bridge: Dump vlan information from a bridge port Vlad Yasevich
2013-01-09 17:18 ` [PATCH net-next v5 14/14] bridge: Add vlan support for local fdb entries Vlad Yasevich

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=50EF660B.2090500@redhat.com \
    --to=vyasevic@redhat.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --cc=shmulik.ladkani@gmail.com \
    --cc=stephen@redhat.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).