From: David Miller <davem@davemloft.net>
To: buytenh@marvell.com
Cc: shemminger@vyatta.com, netdev@vger.kernel.org
Subject: Re: [PATCH 4/8] dsa: convert to net_device_ops
Date: Tue, 06 Jan 2009 10:43:44 -0800 (PST) [thread overview]
Message-ID: <20090106.104344.130715147.davem@davemloft.net> (raw)
In-Reply-To: <20090106060705.GG4414@server.marvell.com>
From: Lennert Buytenhek <buytenh@marvell.com>
Date: Mon, 5 Jan 2009 22:07:05 -0800
> On Mon, Jan 05, 2009 at 12:14:46PM -0800, Stephen Hemminger wrote:
>
> > - slave_dev->open = dsa_slave_open;
> > - slave_dev->stop = dsa_slave_close;
> > - slave_dev->change_rx_flags = dsa_slave_change_rx_flags;
> > - slave_dev->set_rx_mode = dsa_slave_set_rx_mode;
> > - slave_dev->set_multicast_list = dsa_slave_set_rx_mode;
> > - slave_dev->set_mac_address = dsa_slave_set_mac_address;
> > - slave_dev->do_ioctl = dsa_slave_ioctl;
> > + slave_dev->netdev_ops = &dsa_netdev_ops;
> > SET_NETDEV_DEV(slave_dev, parent);
> > slave_dev->vlan_features = master->vlan_features;
>
> Can you make three separate sets of netdevice ops, one for each of the
> tagging formats? On the platforms this driver is used, packet forwarding
> performance matters a _lot_, and I'm pretty sure that adding an extra
> function call indirection in the TX path will translate to a directly
> measurable performance loss.
Agreed, that's probably the way this should be handled.
I'll drop this patch while this issue is being worked out.
next prev parent reply other threads:[~2009-01-06 18:43 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-05 20:14 [PATCH 0/8] More net_device ops Stephen Hemminger
2009-01-05 20:14 ` [PATCH 2/8] bonding: use net_device_ops Stephen Hemminger
2009-01-06 18:42 ` David Miller
2009-01-05 20:14 ` [PATCH 3/8] wireless: convert wireless ioctl to net_device_ops Stephen Hemminger
[not found] ` <20090105201514.442703045-ZtmgI6mnKB3QT0dZR+AlfA@public.gmane.org>
2009-01-06 18:42 ` David Miller
2009-01-05 20:14 ` [PATCH 4/8] dsa: convert " Stephen Hemminger
[not found] ` <20090106060705.GG4414@server.marvell.com>
2009-01-06 18:43 ` David Miller [this message]
2009-01-06 22:51 ` Stephen Hemminger
2009-01-07 0:45 ` David Miller
2009-01-05 20:14 ` [PATCH 5/8] virtio: " Stephen Hemminger
2009-01-06 9:40 ` Mark McLoughlin
2009-01-06 18:44 ` David Miller
2009-01-05 20:14 ` [PATCH 6/8] xen-netfront: " Stephen Hemminger
2009-01-06 0:17 ` Jeremy Fitzhardinge
2009-01-06 18:45 ` David Miller
2009-01-05 20:14 ` [PATCH 7/8] infiniband: driver API update Stephen Hemminger
2009-01-05 21:02 ` Roland Dreier
2009-01-05 21:22 ` [ofa-general] [PATCH 1/3] infiniband: amso100 convert to net_device_ops Stephen Hemminger
2009-01-05 21:22 ` [ofa-general] [PATCH 2/3] infiniband: nes_nic " Stephen Hemminger
2009-01-05 21:23 ` [ofa-general] [PATCH 3/3] infiniband: ipoib " Stephen Hemminger
2009-01-06 5:07 ` Roland Dreier
2009-01-06 18:46 ` [ofa-general] " David Miller
2009-01-06 18:45 ` [ofa-general] Re: [PATCH 7/8] infiniband: driver API update David Miller
2009-01-05 20:14 ` [PATCH 8/8] sch_teql: convert to net_device_ops Stephen Hemminger
2009-01-06 18:46 ` David Miller
[not found] ` <20090105201514.192918670@vyatta.com>
2009-01-06 18:41 ` [PATCH 1/8] irda: convert to internal stats 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=20090106.104344.130715147.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=buytenh@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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).