From: Stephen Suryaputra <ssuryaextr@gmail.com>
To: Brodie Greenfield <brodie.greenfield@alliedtelesis.co.nz>
Cc: davem@davemloft.net, stephen@networkplumber.org,
kuznet@ms2.inr.ac.ru, yoshfuji@linux-ipv6.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
chris.packham@alliedtelesis.co.nz,
luuk.paulussen@alliedtelesis.co.nz
Subject: Re: [PATCH 1/2] ipmr: Make cache queue length configurable
Date: Fri, 26 Jul 2019 06:10:09 -0400 [thread overview]
Message-ID: <20190726101009.GA2657@ubuntu> (raw)
In-Reply-To: <20190725204230.12229-2-brodie.greenfield@alliedtelesis.co.nz>
On Fri, Jul 26, 2019 at 08:42:29AM +1200, Brodie Greenfield wrote:
> We want to be able to keep more spaces available in our queue for
> processing incoming multicast traffic (adding (S,G) entries) - this lets
> us learn more groups faster, rather than dropping them at this stage.
>
> Signed-off-by: Brodie Greenfield <brodie.greenfield@alliedtelesis.co.nz>
Our system can use this. The patch applied cleanly to my net-next
sandbox. Thank you.
Reviewed-by: Stephen Suryaputra <ssuryaextr@gmail.com>
next prev parent reply other threads:[~2019-07-26 10:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 20:42 [PATCH 0/2] Make ipmr queue length configurable Brodie Greenfield
2019-07-25 20:42 ` [PATCH 1/2] ipmr: Make cache " Brodie Greenfield
2019-07-26 10:10 ` Stephen Suryaputra [this message]
2019-07-26 11:05 ` Nikolay Aleksandrov
2019-07-26 11:15 ` Nikolay Aleksandrov
2019-07-27 17:03 ` Stephen Suryaputra
2019-07-25 20:42 ` [PATCH 2/2] ip6mr: " Brodie Greenfield
2019-07-26 10:10 ` Stephen Suryaputra
2019-07-27 20:18 ` [PATCH 0/2] Make ipmr " David Miller
-- strict thread matches above, loose matches on Subject: below --
2019-03-07 4:57 Brodie Greenfield
2019-03-07 4:57 ` [PATCH 1/2] ipmr: Make cache " Brodie Greenfield
2019-03-06 20:19 [PATCH 0/2] Make ipmr " Brodie Greenfield
2019-03-06 20:19 ` [PATCH 1/2] ipmr: Make cache " Brodie Greenfield
2019-03-07 15:40 ` Stephen Hemminger
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=20190726101009.GA2657@ubuntu \
--to=ssuryaextr@gmail.com \
--cc=brodie.greenfield@alliedtelesis.co.nz \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=davem@davemloft.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=luuk.paulussen@alliedtelesis.co.nz \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=yoshfuji@linux-ipv6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.