netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Fastabend <john.r.fastabend@intel.com>
To: Roopa Prabhu <roprabhu@cisco.com>
Cc: jhs@mojatatu.com, shemminger@vyatta.com,
	bhutchings@solarflare.com, davem@davemloft.net,
	jeffrey.t.kirsher@intel.com, netdev@vger.kernel.org,
	mst@redhat.com, chrisw@redhat.com, gregory.v.rose@intel.com,
	kvm@vger.kernel.org, sri@us.ibm.com, chealy@imsco-us.com
Subject: Re: [net-next PATCH v0 3/5] net: add fdb generic dump routine
Date: Mon, 26 Mar 2012 14:41:27 -0700	[thread overview]
Message-ID: <4F70E287.80402@intel.com> (raw)
In-Reply-To: <CB94671B.49E3F%roprabhu@cisco.com>

On 3/25/2012 6:09 AM, Roopa Prabhu wrote:
> 
> 
> 
> On 3/18/12 11:52 PM, "John Fastabend" <john.r.fastabend@intel.com> wrote:
> 
>> This adds a generic dump routine drivers can call. It
>> should be sufficient to handle any bridging model that
>> uses the unicast address list. This should be most SR-IOV
>> enabled NICs.
>>
>> Signed-off-by: John Fastabend <john.r.fastabend@intel.com>
>> ---
>>

[...]

>> +/**
>> + * ndo_dflt_fdb_dump: default netdevice operation to dump an FDB table.
>> + * @nlh: netlink message header
>> + * @dev: netdevice
>> + *
>> + * Default netdevice operation to dump the existing unicast address list.
>> + * Returns zero on success.
>> + */
>> +int ndo_dflt_fdb_dump(struct sk_buff *skb,
>> +        struct netlink_callback *cb,
>> +        struct net_device *dev,
>> +        int idx)
>> +{
>> + struct netdev_hw_addr *ha;
>> + struct nlmsghdr *nlh;
>> + struct ndmsg *ndm;
>> + u32 pid, seq;
>> +
>> + pid = NETLINK_CB(cb->skb).pid;
>> + seq = cb->nlh->nlmsg_seq;
>> +
>> + netif_addr_lock_bh(dev);
>> + list_for_each_entry(ha, &dev->uc.list, list) {
>> +  if (idx < cb->args[0])
>> +   goto skip;
> 
> Any reason why its only uc ?. What about mc ?

Sure this might be useful to know for embedded devices
and likely more useful for the macvlan driver. I'll add
it in the next version.

Thanks,
John



  reply	other threads:[~2012-03-26 21:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19  6:51 [net-next PATCH v0 0/5] Series short description John Fastabend
2012-03-19  6:51 ` [net-next PATCH v0 2/5] net: addr_list: add exclusive dev_uc_add John Fastabend
2012-03-25 13:07   ` Roopa Prabhu
2012-03-19  6:52 ` [net-next PATCH v0 3/5] net: add fdb generic dump routine John Fastabend
2012-03-25 13:09   ` Roopa Prabhu
2012-03-26 21:41     ` John Fastabend [this message]
2012-03-19  6:52 ` [net-next PATCH v0 4/5] ixgbe: enable FDB netdevice ops John Fastabend
2012-03-19 22:46   ` Jeff Kirsher
2012-03-19  6:52 ` [net-next PATCH v0 5/5] ixgbe: allow RAR table to be updated in promisc mode John Fastabend
2012-03-19 22:44   ` Jeff Kirsher
2012-03-19 22:38 ` [net-next PATCH v0 0/5] Series short description David Miller
2012-03-19 22:55   ` Stephen Hemminger
2012-03-20  0:27     ` John Fastabend
2012-03-20  0:35       ` David Miller
2012-03-20  2:49         ` John Fastabend
2012-03-20  2:51           ` Stephen Hemminger

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=4F70E287.80402@intel.com \
    --to=john.r.fastabend@intel.com \
    --cc=bhutchings@solarflare.com \
    --cc=chealy@imsco-us.com \
    --cc=chrisw@redhat.com \
    --cc=davem@davemloft.net \
    --cc=gregory.v.rose@intel.com \
    --cc=jeffrey.t.kirsher@intel.com \
    --cc=jhs@mojatatu.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=roprabhu@cisco.com \
    --cc=shemminger@vyatta.com \
    --cc=sri@us.ibm.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).