All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Frederick, Fabian" <Fabian.Frederick@prov-liege.be>
To: jimis@gmx.net, linux-kernel@vger.kernel.org
Subject: RE: Feature proposal (scheduling related)
Date: Wed, 23 Jul 2003 14:42:08 +0200	[thread overview]
Message-ID: <D9B4591FDBACD411B01E00508BB33C1B01BCA5C4@mesadm.epl.prov-liege.be> (raw)

Jimis,

	I have been thinking about some /etc/nice file where kernel could
pick up process nice
when doing the sys_execve stuff.Maybe it could help ...

Regards,
Fabian

-----Message d'origine-----
De : jimis@gmx.net [mailto:jimis@gmx.net]
Envoyé : mercredi 23 juillet 2003 12:58
À : linux-kernel@vger.kernel.org
Objet : Feature proposal (scheduling related)


With the current scheduler we can prioritize the CPU usage for each process.

What I think would be extremely useful (as I have needed it many times) is
the 
scheduling of disk I/O and net I/O traffic. 2 examples showing the
importance 
(the numbers are estimations just to explain whati I mean):

1)I 'm connected to the internet via dial-up, therefore I only have 40 kbits
of 
bandwidth available. What I want to do is listen to icecast radio via xmms
(at 
22 kbits), download the kernel sources with wget, and browse the web at the
same 
time. Currently I think that this is *impossible* (correct me if I'm wrong)
as 
the radio will be full of pauses and the browsing experience painfully slow.

What I would like to be able to do (let's suppose nice has the --net option
to 
set net I/O priority):
$ nice --net -1 xmms
$ nice --net 1 wget ftp://.../KernelSources.tar.bz2
$ mozilla
This way, xmms which has top priority whould always get the 22kbits it
needs. 
What remains should go to the browser when I ask for a web page, and when
the 
browser doesn't request anything (let's say I'm reading a big doc in tldp)
what 
remains should go to wget. Wget has lower priority and won't irritate the 
browsing experience, though the file will be downloaded when there is free 
bandwidth.

2) Normally mozilla starts in 5 seconds after intense disk I/O to load all 
needed libraries. If I run in the background a long disk intense process
(like find / -name 'whatever' -xdev) loading mozilla could need 20 boring 
seconds, or doing other simple tasks might be irritating slow. What I would
like 
to be able to do is (once again let's suppose nice has the --disk option to
set 
disk I/O priority):
$ nice --disk 1 find / -name 'whatever' -xdev
$ mozilla
and load mozilla ,which has the default disk priority 0, fast. The scheduler

should give to mozilla most disk troughput when it needs it.

Notes:
1) PLEASE CC REPLIES BACK TO ME since I 'm not subscribed to the list (I
can't 
stand the traffic). However I 'll be checking periodically the list via
NNTP.
2) As I have no idea of kernel programming I hope what I propose is
aplicable 
and relevant to the kernel, as I believe. Sorry if not.
3) I hope what I propose is implementable using the existing scheduler. It
would 
be nice to have one scheduler to handle them all.
4) I believe that these features don't need a lot of CPU power because the
disk 
and net I/O troughput are relatively slow.
5) If you think that UNIX tradition forbits what I propose I must say that
these 
features could be invisible to programs, setting the new  priorities to the 
default 0 or maybe to the same number as CPU priority.

Thank you very much for your time,
Dimitris


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

             reply	other threads:[~2003-07-23 12:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-23 12:42 Frederick, Fabian [this message]
     [not found] <cpvY.4hH.25@gated-at.bofh.it>
2003-07-23 11:54 ` Feature proposal (scheduling related) Ihar "Philips" Filipau
  -- strict thread matches above, loose matches on Subject: below --
2003-07-23 10:57 jimis
2003-07-23 11:24 ` David M. Wilson
2003-07-23 11:43 ` Pavel Machek
2003-07-25 20:24   ` Marcelo Tosatti
2003-07-28  9:29     ` Pavel Machek
2003-07-23 14:17 ` Valdis.Kletnieks
2003-07-23 14:23   ` Alan Cox
2003-07-23 15:10     ` Richard B. Johnson
2003-07-23 15:13       ` Antonio Vargas
2003-07-23 16:55         ` Disconnect
2003-07-23 17:22           ` David S. Miller
2003-07-23 14:47   ` Greg Stark
2003-07-23 22:17   ` jimis
2003-07-24  0:58     ` Mike Fedyk
2003-07-24  4:04   ` Andre Tomt

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=D9B4591FDBACD411B01E00508BB33C1B01BCA5C4@mesadm.epl.prov-liege.be \
    --to=fabian.frederick@prov-liege.be \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.