From: Dimitris Apostolou <jimis@gmx.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Feature proposal (scheduling related) -- conclusion
Date: Wed, 30 Jul 2003 00:07:45 +0300 [thread overview]
Message-ID: <3F26E221.6060306@gmx.net> (raw)
In-Reply-To: <200307291958.h6TJw43o030219@turing-police.cc.vt.edu>
Valdis.Kletnieks@vt.edu wrote:
>
> So you want to use a number that controls the CPU scheduling to force the network
> scheduling to go along? That's a bad idea waiting to happen.
>
Read my initial posting, what I propose is defining priorities for net and disk
I/O independant to CPU priority
next prev parent reply other threads:[~2003-07-29 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 19:28 Feature proposal (scheduling related) -- conclusion jimis
2003-07-29 19:58 ` Valdis.Kletnieks
2003-07-29 21:07 ` Dimitris Apostolou [this message]
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=3F26E221.6060306@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