From: Ben Hutchings <bhutchings@solarflare.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>
Subject: Re: [PATCH 6/7] neigh: Add device constructor/destructor capability.
Date: Thu, 1 Dec 2011 19:08:35 +0000 [thread overview]
Message-ID: <1322766515.2797.0.camel@bwh-desktop> (raw)
In-Reply-To: <20111130.224151.1479303742039627135.davem@davemloft.net>
On Wed, 2011-11-30 at 22:41 -0500, David Miller wrote:
> If the neigh entry has device private state, it will need
> constructor/destructor ops.
>
> Signed-off-by: David S. Miller <davem@davemloft.net>
> ---
> include/linux/netdevice.h | 2 ++
> net/core/neighbour.c | 15 ++++++++++++++-
> 2 files changed, 16 insertions(+), 1 deletions(-)
>
> diff --git a/include/linux/netdevice.h b/include/linux/netdevice.h
> index 5462c2c..1c4ddb3 100644
> --- a/include/linux/netdevice.h
> +++ b/include/linux/netdevice.h
> @@ -974,6 +974,8 @@ struct net_device_ops {
> netdev_features_t features);
> int (*ndo_set_features)(struct net_device *dev,
> netdev_features_t features);
> + int (*ndo_neigh_construct)(struct neighbour *n);
> + int (*ndo_neigh_destroy)(struct neighbour *n);
ndo_neigh_destroy should return void, since the return value is not
used:
[...]
> @@ -707,7 +717,10 @@ void neigh_destroy(struct neighbour *neigh)
> skb_queue_purge(&neigh->arp_queue);
> neigh->arp_queue_len_bytes = 0;
>
> - dev_put(neigh->dev);
> + if (dev->netdev_ops->ndo_neigh_destroy)
> + dev->netdev_ops->ndo_neigh_destroy(neigh);
> +
> + dev_put(dev);
> neigh_parms_put(neigh->parms);
>
> NEIGH_PRINTK2("neigh %p is destroyed.\n", neigh);
--
Ben Hutchings, Staff Engineer, Solarflare
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2011-12-01 19:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 3:41 [PATCH 6/7] neigh: Add device constructor/destructor capability David Miller
2011-12-01 19:08 ` Ben Hutchings [this message]
2011-12-01 19:16 ` David Miller
-- strict thread matches above, loose matches on Subject: below --
2011-07-25 10:01 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=1322766515.2797.0.camel@bwh-desktop \
--to=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).