All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Juuso Oikarinen <juuso.oikarinen@nokia.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [RFC PATCH] mac80211: Add support for hardware ARP query filtering
Date: Wed, 26 May 2010 13:19:14 +0200	[thread overview]
Message-ID: <1274872754.3658.3.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1274872467.5277.1783.camel@wimaxnb.nmp.nokia.com>

On Wed, 2010-05-26 at 14:14 +0300, Juuso Oikarinen wrote:

> > > +static inline int drv_configure_ip_filter(struct ieee80211_hw *hw,
> > > +					  struct in_ifaddr *ifa_list)
> > > +{
> > > +	struct ieee80211_local *local = hw_to_local(hw);
> > > +	int ret = 0;
> > > +
> > > +	if (local->ops->configure_ip_filter)
> > > +		ret = local->ops->configure_ip_filter(hw, ifa_list);
> > > +	return ret;
> > > +}
> > 
> > Tracing would be nice, you should even able able to trace all addresses
> > in a variable-length array.
> > 
> 
> I looked into the tracing. I still prefer using the ifa_list directly as
> argument to the driver, and not copy the addresses in it to another
> array.
> 
> The ifa_list is a linked list, and does AFAIK does not directly fit into
> the tracing infrasturcture.
> 
> Hence I added a trace for this op, but omitted tracing the IP addresses.

Yeah, that's fine ... it later occurred to me that I also left that out
for the multicast list for exactly this reason.

johannes


      reply	other threads:[~2010-05-26 11:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-25  7:48 [RFC PATCH] mac80211: Add support for hardware ARP query filtering Juuso Oikarinen
2010-05-25  9:13 ` Johannes Berg
2010-05-25  9:31   ` Juuso Oikarinen
2010-05-25 11:25     ` Johannes Berg
2010-05-25 11:34       ` Juuso Oikarinen
2010-05-26 11:14   ` Juuso Oikarinen
2010-05-26 11:19     ` Johannes Berg [this message]

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=1274872754.3658.3.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=juuso.oikarinen@nokia.com \
    --cc=linux-wireless@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 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.