From: Sameer Rahmani <lxsameer@lxsameer.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Share network traffic between process with respect to a priority number.
Date: Wed, 25 Jul 2012 11:21:14 +0430 [thread overview]
Message-ID: <500F9762.1090702@lxsameer.com> (raw)
Hi guys
for years i have problems with sharing my network bandwidth between my
processes. when one of my running processes (e.g axel) start to download
data my other processes that needs bandwidth stop working (because they
can't download their data) . i know that there is some tools like lartc
but i was thinking about a priority value like NICE for this matter.
kernel will share the bandwidth between process with respect to their
network priority number let's call it NNICE ( or what ever ) . The
process with highest NNICE will use the highest bandwidth.
It's just an raw idea, i want to know your idea about the basic , and
improve it.
What do you think?
With respect
Sameer Rahmani
next reply other threads:[~2012-07-25 6:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-25 6:51 Sameer Rahmani [this message]
2012-07-25 7:54 ` Share network traffic between process with respect to a priority number Eric Dumazet
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=500F9762.1090702@lxsameer.com \
--to=lxsameer@lxsameer.com \
--cc=netdev@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