All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Devarajan <ndev2021@gmail.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>
Cc: Cong Wang <xiyou.wangcong@gmail.com>,
	Jiri Pirko <jiri@resnulli.us>, David Miller <davem@davemloft.net>,
	netdev@vger.kernel.org, doucette@bu.edu, michel@digirati.com.br,
	Alexander Duyck <alexander.duyck@gmail.com>
Subject: Re: [PATCH v2 net-next] net/sched: add skbprio scheduler
Date: Tue, 26 Jun 2018 06:04:09 +0530	[thread overview]
Message-ID: <20180626003408.GA4645@gmail.com> (raw)
In-Reply-To: <8076dc76-9f93-bebd-8376-28b8b4aa756b@mojatatu.com>

On Sun, Jun 24, 2018 at 11:43:07AM -0400, Jamal Hadi Salim wrote:
> On 23/06/18 04:47 PM, Nishanth Devarajan wrote:
> [..]
> 
> >+	/* Drop the packet at the tail of the lowest priority qdisc. */
> >+	lp_qdisc = &q->qdiscs[lp];
> >+	to_drop = __skb_dequeue_tail(lp_qdisc);
> >+	BUG_ON(!to_drop);
> >+	qdisc_qstats_backlog_dec(sch, to_drop);
> >+	qdisc_drop(to_drop, sch, to_free);
> >+
> 
> Maybe also increase overlimit stat here? It will keep track
> of low prio things dropped because you were congested.
> Such a stat helps when debugging or collecting analytics.
> 
> Per Alex's comment, how about:
> 
> -----------
> Skbprio (SKB Priority Queue) is a queueing discipline that
> prioritizes packets according to their skb->priority field.
> Under congestion, already-enqueued lower priority packets
> will be dropped to make space available for higher priority
> packets. Skbprio was conceived as a solution for
> denial-of-service defenses that need to route packets with
> different priorities as a means to overcome DoS attacks
> as described in paper xxxx...
> 
> 
> cheers,
> jamal

Sounds good, will make some changes in v3.

Thanks,
Nishanth

  reply	other threads:[~2018-06-26  0:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-23 20:47 [PATCH v2 net-next] net/sched: add skbprio scheduler Nishanth Devarajan
2018-06-23 21:43 ` Cong Wang
2018-06-25 23:27   ` Nishanth Devarajan
2018-06-23 22:10 ` Alexander Duyck
2018-06-26  0:11   ` Nishanth Devarajan
2018-06-24 15:43 ` Jamal Hadi Salim
2018-06-26  0:34   ` Nishanth Devarajan [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-06 15:40 Nishanth Devarajan

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=20180626003408.GA4645@gmail.com \
    --to=ndev2021@gmail.com \
    --cc=alexander.duyck@gmail.com \
    --cc=davem@davemloft.net \
    --cc=doucette@bu.edu \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=michel@digirati.com.br \
    --cc=netdev@vger.kernel.org \
    --cc=xiyou.wangcong@gmail.com \
    /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.