From: Oliver Neukum <oliver@neukum.org>
To: cschumpf@gmx.net, linux-kernel@vger.kernel.org
Subject: Re: Patch or module?
Date: Tue, 19 Feb 2002 20:08:32 +0100 [thread overview]
Message-ID: <16dFd0-1wqRZwC@fmrl09.sul.t-online.com> (raw)
In-Reply-To: <18920.1014143039@www57.gmx.net>
In-Reply-To: <18920.1014143039@www57.gmx.net>
On Tuesday 19 February 2002 19:23, cschumpf@gmx.net wrote:
> If thats not the right group to discuss that, please let me know.
>
> I would like to write an IO-Bandwidth-Limiter on per Process and per
> User-Basis for a few disk drives. I can either patch the kernel functions
> read/write and enhance the task- and user-structure and globally check if
> the correct devices are adressed or I can write my own module, twist
> pointers from the filesystems on the drives and store the information about
> users and tasks there.
You cannot do this on the device level as the writing task is not identical
to the task actual having caused the requirement to do IO.
HTH
Oliver
next prev parent reply other threads:[~2002-02-19 19:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 18:23 cschumpf
2002-02-19 19:08 ` Oliver Neukum [this message]
2002-02-19 18:27 cschumpf
2002-02-19 18:27 cschumpf
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=16dFd0-1wqRZwC@fmrl09.sul.t-online.com \
--to=oliver@neukum.org \
--cc=cschumpf@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
all inboxes | Powered by JetHome®