netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: netdev@vger.kernel.org
Cc: stephen@networkplumber.org, edumazet@google.com,
	Dave Taht <dave.taht@gmail.com>
Subject: [PATCH v3 net-next 0/3] netem: add nsec scheduling and slot feature
Date: Wed,  8 Nov 2017 15:12:25 -0800	[thread overview]
Message-ID: <1510182748-10991-1-git-send-email-dave.taht@gmail.com> (raw)

This patch series converts netem away from the old "ticks" interface and
userspace API, and adds support for a new "slot" feature intended to
emulate bursty macs such as WiFi and LTE better.

Changes since v2:
Use u64 for packet_len_sched_time()
Use simpler max(time_to_send,q->slot.slot_next)

Changes since v1:
Always pass new nanosecond APIs to userspace

Dave Taht (3):
  netem: convert to qdisc_watchdog_schedule_ns
  netem: add uapi to express delay and jitter in nanoseconds
  netem: support delivering packets in delayed time slots

 include/uapi/linux/pkt_sched.h |  10 +++
 net/sched/sch_netem.c          | 140 ++++++++++++++++++++++++++++++++---------
 2 files changed, 121 insertions(+), 29 deletions(-)

-- 
2.7.4

             reply	other threads:[~2017-11-08 23:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-08 23:12 Dave Taht [this message]
2017-11-08 23:12 ` [PATCH v3 net-next 1/3] netem: convert to qdisc_watchdog_schedule_ns Dave Taht
2017-11-08 23:12 ` [PATCH v3 net-next 2/3] netem: add uapi to express delay and jitter in nanoseconds Dave Taht
2017-11-08 23:24   ` Stephen Hemminger
2017-11-08 23:36     ` Dave Taht
2017-11-08 23:43       ` Eric Dumazet
2017-11-08 23:12 ` [PATCH v3 net-next 3/3] netem: support delivering packets in delayed time slots Dave Taht
2017-11-13  1:16 ` [PATCH v3 net-next 0/3] netem: add nsec scheduling and slot feature 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=1510182748-10991-1-git-send-email-dave.taht@gmail.com \
    --to=dave.taht@gmail.com \
    --cc=edumazet@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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).