netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bastian Bloessl <basti@b-bl.de>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, jarkao2@gmail.com
Subject: Re: [PATCH 5/9]: sch_netem: Use requeue list instead of ops->requeue()
Date: Tue, 19 Aug 2008 19:36:09 +0200	[thread overview]
Message-ID: <48AB0489.8060107@b-bl.de> (raw)
In-Reply-To: <20080818.013702.111675433.davem@davemloft.net>

David Miller wrote:
> sch_netem: Use requeue list instead of ops->requeue()
> 
> This code just wants to make this packet the "front" one, and that's
> just as simply done by queueing to the ->requeue list.
> 

Hi,
I think that might make some difference.
Suppose we have an upper qdisc that dequeues from netem and
puts the packet in it's requeue-list. But after that another
packet could arrive that should be send earlier (delay
distribution, reordering).
As far as I understand it the requeued packet would now
be send before the other.

> --- a/net/sched/sch_netem.c
> +++ b/net/sched/sch_netem.c
> @@ -233,7 +233,8 @@ static int netem_enqueue(struct sk_buff *skb, struct Qdisc *sch)
>  		 */
>  		cb->time_to_send = psched_get_time();
>  		q->counter = 0;
> -		ret = q->qdisc->ops->requeue(skb, q->qdisc);
> +		__skb_queue_tail(&q->qdisc->requeue, skb);

I think this should be __skb_queue_head() because in it's
requeue-list netem has packets that it doesn't want to send yet. So
their time_to_send is likely to be in the future. But reordered
packets have current time as time_to_send.

Or did I get it wrong?

Regards
Bastian Bloessl

      reply	other threads:[~2008-08-19 17:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18  8:37 [PATCH 5/9]: sch_netem: Use requeue list instead of ops->requeue() David Miller
2008-08-19 17:36 ` Bastian Bloessl [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=48AB0489.8060107@b-bl.de \
    --to=basti@b-bl.de \
    --cc=davem@davemloft.net \
    --cc=jarkao2@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).