From: Cong Wang <xiyou.wangcong@gmail.com>
To: netdev@vger.kernel.org
Cc: john.fastabend@gmail.com, Cong Wang <xiyou.wangcong@gmail.com>
Subject: [Patch net-next 3/3] net_sched: implement ->change_tx_queue_len() for pfifo_fast
Date: Fri, 19 Jan 2018 15:09:33 -0800 [thread overview]
Message-ID: <20180119230933.10009-4-xiyou.wangcong@gmail.com> (raw)
In-Reply-To: <20180119230933.10009-1-xiyou.wangcong@gmail.com>
pfifo_fast used to drop based on qdisc_dev(qdisc)->tx_queue_len,
so we have to resize skb array when we change tx_queue_len.
Other qdiscs which read tx_queue_len are fine because they
all save it to sch->limit or somewhere else in qdisc during init.
They don't have to implement this, it is nicer if they do so
that users don't have to re-configure qdisc after changing
tx_queue_len.
Cc: John Fastabend <john.fastabend@gmail.com>
Signed-off-by: Cong Wang <xiyou.wangcong@gmail.com>
---
net/sched/sch_generic.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/net/sched/sch_generic.c b/net/sched/sch_generic.c
index 30aaeb3c1bf1..7c48a6942238 100644
--- a/net/sched/sch_generic.c
+++ b/net/sched/sch_generic.c
@@ -763,6 +763,18 @@ static void pfifo_fast_destroy(struct Qdisc *sch)
}
}
+static void pfifo_fast_change_tx_queue_len(struct Qdisc *sch, unsigned int new_len)
+{
+ struct pfifo_fast_priv *priv = qdisc_priv(sch);
+ int prio;
+
+ for (prio = 0; prio < PFIFO_FAST_BANDS; prio++) {
+ struct skb_array *q = band2list(priv, prio);
+
+ skb_array_resize(q, new_len, GFP_KERNEL);
+ }
+}
+
struct Qdisc_ops pfifo_fast_ops __read_mostly = {
.id = "pfifo_fast",
.priv_size = sizeof(struct pfifo_fast_priv),
@@ -773,6 +785,7 @@ struct Qdisc_ops pfifo_fast_ops __read_mostly = {
.destroy = pfifo_fast_destroy,
.reset = pfifo_fast_reset,
.dump = pfifo_fast_dump,
+ .change_tx_queue_len = pfifo_fast_change_tx_queue_len,
.owner = THIS_MODULE,
.static_flags = TCQ_F_NOLOCK | TCQ_F_CPUSTATS,
};
--
2.13.0
prev parent reply other threads:[~2018-01-19 23:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 23:09 [Patch net-next 0/3] net_sched: reflect tx_queue_len change for pfifo_fast Cong Wang
2018-01-19 23:09 ` [Patch net-next 1/3] net: introduce helper dev_change_tx_queue_len() Cong Wang
2018-01-21 4:52 ` John Fastabend
2018-01-21 20:30 ` Cong Wang
2018-01-21 22:09 ` John Fastabend
2018-01-19 23:09 ` [Patch net-next 2/3] net_sched: plug in qdisc ops change_tx_queue_len Cong Wang
2018-01-21 22:12 ` John Fastabend
2018-01-22 22:44 ` Cong Wang
2018-01-23 18:07 ` Cong Wang
2018-01-23 18:17 ` John Fastabend
2018-01-23 18:17 ` John Fastabend
2018-01-19 23:09 ` Cong Wang [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=20180119230933.10009-4-xiyou.wangcong@gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=john.fastabend@gmail.com \
--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).