From: cschumpf@gmx.net
To: linux-kernel@vger.kernel.org
Subject: Patch or module?
Date: Tue, 19 Feb 2002 19:27:17 +0100 (MET) [thread overview]
Message-ID: <24364.1014143237@www57.gmx.net> (raw)
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.
I like the second approach way better, but its maybe slower. I have to do an
extra search in my structures for user and task ids, which is maybe more
expensive than an 'if' in the read/write-funktion.
Any guidelines? Any recommendations?
Thanks
--
GMX - Die Kommunikationsplattform im Internet.
http://www.gmx.net
next reply other threads:[~2002-02-19 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 18:27 cschumpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-19 18:27 Patch or module? cschumpf
2002-02-19 18:23 cschumpf
2002-02-19 19:08 ` Oliver Neukum
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=24364.1014143237@www57.gmx.net \
--to=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