From: Patrick McHardy <kaber@trash.net>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: vlan 03/07: Add ethtool support
Date: Mon, 07 Jul 2008 18:59:45 +0200 [thread overview]
Message-ID: <48724B81.2070708@trash.net> (raw)
In-Reply-To: <20080707165217.GC28029@solarflare.com>
Ben Hutchings wrote:
> Patrick McHardy wrote:
>> vlan: Add ethtool support
>>
>> Add ethtool support for querying the device for offload settings.
>>
>> Signed-off-by: Patrick McHardy <kaber@trash.net>
> [...]
>> +static u32 vlan_ethtool_get_rx_csum(struct net_device *dev)
>> +{
>> + const struct vlan_dev_info *vlan = vlan_dev_info(dev);
>> + struct net_device *real_dev = vlan->real_dev;
>> +
>> + if (real_dev->ethtool_ops == NULL ||
>> + real_dev->ethtool_ops->get_rx_csum == NULL)
>> + return 0;
>> + return real_dev->ethtool_ops->get_rx_csum(real_dev);
>
> But we don't know whether RX checksum offload applies to VLAN-tagged
> packets (or, admittedly, any specific protocol). It would be nice if there
> was a feature flag for this so it could be advertised in vlan_features.
True, for now the assumption is that it works for VLANs.
I don't think that assumption is unreasonable, but I can
look into a separate flag for this.
>
>> +}
>> +
>> +static const struct ethtool_ops vlan_ethtool_ops = {
>> + .get_link = ethtool_op_get_link,
>> + .get_rx_csum = vlan_ethtool_get_rx_csum,
>
> Can't we also add:
>
> .get_tx_csum = ethtool_op_get_tx_csum,
> .get_sg = ethtool_op_get_sg,
> .get_tso = ethtool_op_get_tso,
> .get_flags = ethtool_op_get_flags,
Besides get_flags all of these are handled by default handlers.
What is get_flags used for?
next prev parent reply other threads:[~2008-07-07 16:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 12:35 vlan 00/07: VLAN update part 1 Patrick McHardy
2008-07-07 12:35 ` vlan 01/07: fix network_header/mac_header adjustments Patrick McHardy
2008-07-07 12:36 ` vlan 02/07: Use is_vlan_dev() Patrick McHardy
2008-07-07 12:36 ` vlan 03/07: Add ethtool support Patrick McHardy
2008-07-07 16:52 ` Ben Hutchings
2008-07-07 16:59 ` Patrick McHardy [this message]
2008-07-07 17:21 ` Ben Hutchings
2008-07-07 17:47 ` Patrick McHardy
2008-07-08 13:54 ` Ben Hutchings
2008-07-08 14:01 ` Patrick McHardy
2008-07-07 12:36 ` vlan 04/07: uninline __vlan_hwaccel_rx Patrick McHardy
2008-07-07 12:36 ` vlan 05/07: move struct vlan_dev_info to private header Patrick McHardy
2008-07-07 12:36 ` vlan 06/07: remove useless struct hlist_node declaration from if_vlan.h Patrick McHardy
2008-07-07 12:36 ` vlan 07/07: TCI related type and naming cleanups Patrick McHardy
2008-07-08 10:44 ` vlan 00/07: VLAN update part 1 David Miller
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=48724B81.2070708@trash.net \
--to=kaber@trash.net \
--cc=bhutchings@solarflare.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.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 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).