From: jimis@gmx.net
To: linux-kernel@vger.kernel.org
Subject: Re: Feature proposal (scheduling related) -- conclusion
Date: Tue, 29 Jul 2003 22:28:50 +0300 [thread overview]
Message-ID: <3F26CAF2.8070009@gmx.net> (raw)
Thank you all very much for your answers, I 've learned a lot. However I have
some comments to make concerning the two proposals I made:
1) Network traffic scheduling. I 've studied a little the linux advanced routing
and traffic control HOWTO and the wondershaper script and I think they are
great, I had no idea of this potential. But what I propose is scheduling the
network traffic (at least the outgoing traffic that we can influence directly)
according to the process priority, not according to the traffic type (which is
important but different).
2) Disk I/O scheduling, again according to the process priority. From some posts
I found out that there was a patch that did that, but I don't know where it is
or if it is up to date with newer kernels.
I hope I clarified myself and I believe these features would be useful if
included in the kernel.
Thanks,
Dimitris
P.S. Please forward me any replies
next reply other threads:[~2003-07-29 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 19:28 jimis [this message]
2003-07-29 19:58 ` Feature proposal (scheduling related) -- conclusion Valdis.Kletnieks
2003-07-29 21:07 ` Dimitris Apostolou
2003-07-30 12:21 ` Pavel Machek
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=3F26CAF2.8070009@gmx.net \
--to=jimis@gmx.net \
--cc=linux-kernel@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