netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jon Maxwell <jmaxwell@redhat.com>
To: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
Cc: Jon Maxwell <jmaxwell37@gmail.com>,
	stephen@networkplumber.org, davem@davemloft.net,
	vyasevic@redhat.com, bridge@lists.linux-foundation.org,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	jpirko@redhat.com
Subject: Re: [PATCH net] bridge: notify user space of fdb port change
Date: Fri, 23 May 2014 21:33:48 -0400 (EDT)	[thread overview]
Message-ID: <1655748249.12329071.1400895228522.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <537F0951.5010904@lab.ntt.co.jp>


> I have no more comments except for style problems (bracket position,
> indentation, type mismatch).
> thank you for rewriting :)

np, yes this is a draft but I will make sure complies with checkpatch.pl
before submitting it.

Regards

Jon

> 
> Thanks,
> Toshiaki Makita
> 
> > 
> > $ diff -Naur br_fdb.c br_fdb.c.patch
> > --- br_fdb.c        2014-05-17 12:43:23.346319609 +1000
> > +++ br_fdb.c.patch        2014-05-17 16:54:46.280235728 +1000
> > @@ -487,6 +487,7 @@
> >  {
> >          struct hlist_head *head = &br->hash[br_mac_hash(addr, vid)];
> >          struct net_bridge_fdb_entry *fdb;
> > +        bool fdb_modified = 0;
> >  
> >          /* some users want to always flood. */
> >          if (hold_time(br) == 0)
> > @@ -507,10 +508,16 @@
> >                                          source->dev->name);
> >                  } else {
> >                          /* fastpath: update of existing entry */
> > -                        fdb->dst = source;
> > +                        if (unlikely(source != fdb->dst))
> > +                                {
> > +                                fdb->dst = source;
> > +                                fdb_modified = 1;
> > +                                }
> >                          fdb->updated = jiffies;
> >                          if (unlikely(added_by_user))
> >                                  fdb->added_by_user = 1;
> > +                        if (unlikely(fdb_modified))
> > +                                fdb_notify(br, fdb, RTM_NEWNEIGH);
> >                  }
> >          } else {
> >                  spin_lock(&br->hash_lock);
> > 
> > 
> 

  reply	other threads:[~2014-05-24  1:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13  7:55 [PATCH net] bridge: notify user space of fdb port change Jon Maxwell
2014-05-13 15:16 ` Jiri Pirko
2014-05-13 15:28   ` Stephen Hemminger
2014-05-14  0:34 ` Toshiaki Makita
2014-05-14 21:07   ` Jon Maxwell
2014-05-23  4:59     ` Jon Maxwell
2014-05-23  8:39       ` Toshiaki Makita
2014-05-24  1:33         ` Jon Maxwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-05-16  7:28 Jon Maxwell
2014-05-16  8:08 Jon Maxwell
2014-05-16  8:12 ` Jon Maxwell
2014-05-16  8:54   ` Jon Maxwell

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=1655748249.12329071.1400895228522.JavaMail.zimbra@redhat.com \
    --to=jmaxwell@redhat.com \
    --cc=bridge@lists.linux-foundation.org \
    --cc=davem@davemloft.net \
    --cc=jmaxwell37@gmail.com \
    --cc=jpirko@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=makita.toshiaki@lab.ntt.co.jp \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.org \
    --cc=vyasevic@redhat.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).