From: Martin Lau <kafai@fb.com>
To: David Miller <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <hannes@stressinduktion.org>
Subject: Re: [PATCH RFC v4 net 1/3] ipv6: Remove BACKTRACK macro
Date: Tue, 14 Oct 2014 17:14:11 -0700 [thread overview]
Message-ID: <20141015001409.GB27904@devbig242.prn2.facebook.com> (raw)
In-Reply-To: <20141014.150106.2250383188165649088.davem@davemloft.net>
Hi,
> > +struct fib6_node *fib6_backtrack(struct fib6_node *fn,
> > + struct in6_addr *saddr);
> > +
>
> I am completely mystified why you did this, could you explain the
> logic? I want to know what drove you to make this exported.
>
> I marked it static in my example patch, and there is no caller outside
> of route.c
>
I was thinking this function only works on 'struct fib6_node', so
it belongs to ip6_fib.c more than route.c.
f.e. like fib6_lookup() whose callers are also only in route.c
> Doing this also eliminates inlining opportunitites.
>
> Please keep this private inside of route.c
I will keep it private in route.c and re-submit.
Do you have input on the function signature and also the following two
patches?
Thanks,
--Martin
next prev parent reply other threads:[~2014-10-15 0:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-10 18:48 [PATCH RFC v4 net 0/3]: ipv6: Reduce the number of fib6_lookup() calls from ip6_pol_route() Martin KaFai Lau
2014-10-10 18:48 ` [PATCH RFC v4 net 1/3] ipv6: Remove BACKTRACK macro Martin KaFai Lau
2014-10-14 19:01 ` David Miller
2014-10-15 0:14 ` Martin Lau [this message]
2014-10-15 2:04 ` David Miller
2014-10-10 18:48 ` [PATCH RFC v4 net 2/3] ipv6: Avoid redoing fib6_lookup() for RTF_CACHE hit case Martin KaFai Lau
2014-10-10 18:48 ` [PATCH RFC v4 net 3/3] ipv6: Avoid redo-ing fib6_lookup() with reachable = 0 by saving fn Martin KaFai Lau
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=20141015001409.GB27904@devbig242.prn2.facebook.com \
--to=kafai@fb.com \
--cc=davem@davemloft.net \
--cc=hannes@stressinduktion.org \
--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).