From: David Miller <davem@davemloft.net>
To: horms@verge.net.au
Cc: netdev@vger.kernel.org, bridge@lists.linux-foundation.org,
jpirko@redhat.com, shemminger@linux-foundation.org,
jesse@nicira.com
Subject: Re: [rfc] bridge: is PACKET_LOOPBACK unlikely()?
Date: Sun, 22 Aug 2010 21:14:36 -0700 (PDT) [thread overview]
Message-ID: <20100822.211436.212698198.davem@davemloft.net> (raw)
In-Reply-To: <20100823033532.GA28463@verge.net.au>
From: Simon Horman <horms@verge.net.au>
Date: Mon, 23 Aug 2010 12:35:32 +0900
> While looking at using netdev_rx_handler_register for openvswitch Jesse
> Gross suggested that an unlikely() might be worthwhile in that code.
> I'm interested to see if its appropriate for the bridge code.
>
> Cc: Jesse Gross <jesse@nicira.com>
> Signed-off-by: Simon Horman <horms@verge.net.au>
Seems reasonable to me, applied to net-next-2.6
prev parent reply other threads:[~2010-08-23 4:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-23 3:35 [rfc] bridge: is PACKET_LOOPBACK unlikely()? Simon Horman
2010-08-23 4:14 ` David Miller [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=20100822.211436.212698198.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.linux-foundation.org \
--cc=horms@verge.net.au \
--cc=jesse@nicira.com \
--cc=jpirko@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).