From: Antonio Quartulli <antonio@meshcoding.com>
To: davem@davemloft.net
Cc: netdev@vger.kernel.org, b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] pull request: batman-adv 2014-08-05
Date: Tue, 5 Aug 2014 09:36:24 +0200 [thread overview]
Message-ID: <1407224188-28626-1-git-send-email-antonio@meshcoding.com> (raw)
Hello David,
this is a pull request intended for net-next/linux-3.17 (yeah..it's really
late).
Patches 1, 2 and 4 are really minor changes:
- kmalloc_array is substituted to kmalloc when possible (as suggested by
checkpatch);
- net_ratelimited() is now used properly and the "suppressed" message is not
printed anymore if not needed;
- the internal version number has been increased to reflect our current version.
Patch 3 instead is introducing a change in the metric computation function
by changing the penalty applied at each mesh hop from 15/255 (~6%) to
30/255 (~11%). This change is introduced by Simon Wunderlich after having
observed a performance improvement in several networks when using the new value.
Please pull or let me know of any problem!
Thanks a lot,
Antonio
The following changes since commit e6b92c25d20c64c271ef429bba8febeefb848b5b:
cxgb4i : remove spurious use of rcu (2014-08-02 20:34:33 -0700)
are available in the git repository at:
git://git.open-mesh.org/linux-merge.git tags/batman-adv-for-davem
for you to fetch changes up to 0028c72ec4300997f2d0b73594f391983090463b:
batman-adv: Start new development cycle (2014-08-04 16:03:13 +0200)
----------------------------------------------------------------
Included changes:
- kmalloc_array instead of kmalloc when possible
- avoid log spam due to useless net_ratelimit() invocations
- increase default metric hop penalty from 15 to 30
- update internal version number
----------------------------------------------------------------
André Gaul (1):
batman-adv: remove unnecessary logspam
Antonio Quartulli (1):
batman-adv: prefer kmalloc_array to kmalloc when possible
Simon Wunderlich (2):
batman-adv: increase default hop penalty
batman-adv: Start new development cycle
net/batman-adv/bat_iv_ogm.c | 13 +++++++------
net/batman-adv/distributed-arp-table.c | 3 ++-
net/batman-adv/hash.c | 6 +++---
net/batman-adv/main.h | 22 +++++++++++++++-------
net/batman-adv/routing.c | 18 +++++++++---------
net/batman-adv/soft-interface.c | 2 +-
6 files changed, 37 insertions(+), 27 deletions(-)
next reply other threads:[~2014-08-05 7:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 7:36 Antonio Quartulli [this message]
2014-08-05 7:36 ` [B.A.T.M.A.N.] [PATCH 1/4] batman-adv: prefer kmalloc_array to kmalloc when possible Antonio Quartulli
2014-08-05 7:36 ` [B.A.T.M.A.N.] [PATCH 2/4] batman-adv: remove unnecessary logspam Antonio Quartulli
2014-08-05 7:36 ` [B.A.T.M.A.N.] [PATCH 3/4] batman-adv: increase default hop penalty Antonio Quartulli
2014-08-05 7:36 ` [B.A.T.M.A.N.] [PATCH 4/4] batman-adv: Start new development cycle Antonio Quartulli
2014-08-05 23:40 ` [B.A.T.M.A.N.] pull request: batman-adv 2014-08-05 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=1407224188-28626-1-git-send-email-antonio@meshcoding.com \
--to=antonio@meshcoding.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=davem@davemloft.net \
--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).