From: David Miller <davem@davemloft.net>
To: stephen@networkplumber.org
Cc: nikolay@cumulusnetworks.com, netdev@vger.kernel.org,
roopa@cumulusnetworks.com, bridge@lists.linux-foundation.org
Subject: Re: [PATCH net-next] bridge: avoid unnecessary read of jiffies
Date: Tue, 07 Feb 2017 14:16:30 -0500 (EST) [thread overview]
Message-ID: <20170207.141630.1294831074568265709.davem@davemloft.net> (raw)
In-Reply-To: <20170207084646.70dc888a@xeon-e3>
From: Stephen Hemminger <stephen@networkplumber.org>
Date: Tue, 7 Feb 2017 08:46:46 -0800
> Jiffies is volatile so read it once.
>
> Signed-off-by: Stephen Hemminger <sthemmin@microsoft.com>
Applied, thanks Stephen.
next prev parent reply other threads:[~2017-02-07 19:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-04 17:05 [PATCH net-next 0/4] bridge: improve cache utilization Nikolay Aleksandrov via Bridge
2017-02-04 17:05 ` [PATCH net-next 1/4] bridge: modify bridge and port to have often accessed fields in one cache line Nikolay Aleksandrov
2017-02-04 17:05 ` [PATCH net-next 2/4] bridge: move to workqueue gc Nikolay Aleksandrov
2017-02-04 17:05 ` [PATCH net-next 3/4] bridge: move write-heavy fdb members in their own cache line Nikolay Aleksandrov
2017-02-04 17:05 ` [PATCH net-next 4/4] bridge: fdb: write to used and updated at most once per jiffy Nikolay Aleksandrov
2017-02-07 16:46 ` [PATCH net-next] bridge: avoid unnecessary read of jiffies Stephen Hemminger
2017-02-07 16:56 ` Nikolay Aleksandrov via Bridge
2017-02-07 19:16 ` David Miller [this message]
2017-02-04 21:46 ` [PATCH net-next 0/4] bridge: improve cache utilization Stephen Hemminger
2017-02-04 21:58 ` Nikolay Aleksandrov
2017-02-07 3:53 ` David Miller
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=20170207.141630.1294831074568265709.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=roopa@cumulusnetworks.com \
--cc=stephen@networkplumber.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).