From: Denys Fedoryschenko <denys@visp.net.lb>
To: Michal Soltys <soltys@ziu.info>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH/RFC 1/2] HFSC (7) & (8) documentation + assorted changes
Date: Fri, 27 Feb 2009 17:16:27 +0200 [thread overview]
Message-ID: <200902271716.27811.denys@visp.net.lb> (raw)
In-Reply-To: <dd4be29320bb8ab261489328bde6fb5620dbec1c.1235685021.git.soltys@ziu.info>
It is really VERY VERY great documentation.
Thanks a lot for your efforts!
On Friday 27 February 2009 01:01:31 Michal Soltys wrote:
> This patch adds detailed documentation for HFSC scheduler. It roughly
> follows HFSC paper, but tries to not rely too much on math side of things.
> Post-paper/Linux specific subjects (timer resolution, ul service curve,
> etc.) are also discussed.
next prev parent reply other threads:[~2009-02-27 15:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-26 23:01 [PATCH/RFC 0/2] HFSC & Stab documentation Michal Soltys
2009-02-26 23:01 ` [PATCH/RFC 1/2] HFSC (7) & (8) documentation + assorted changes Michal Soltys
2009-02-27 15:16 ` Denys Fedoryschenko [this message]
2009-02-26 23:01 ` [PATCH/RFC 2/2] Stab " Michal Soltys
2009-04-30 20:04 ` [PATCH/RFC 0/2] HFSC & Stab documentation Denys Fedoryschenko
2009-05-11 14:32 ` Michal Soltys
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=200902271716.27811.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=netdev@vger.kernel.org \
--cc=soltys@ziu.info \
/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).