From: "Rolf Schäuble" <mail@rschaeuble.de>
To: linux-kernel@vger.kernel.org
Subject: Block device driver in user space
Date: 23 Mar 2002 01:44:13 +0100 [thread overview]
Message-ID: <1016844254.1193.31.camel@desktop> (raw)
Hi. I'm thinking about a block device driver which is split between
kernel and user space.
But there are some things that give me a headache:
- Memory pressure:
The system runs out of free RAM. So the block buffer is freed by letting
all the devices write the data. So the userspace part is asked to
process some data. Therefore it might need more RAM, which will increase
the memory pressure. Therefore even more memory needs to be written.
Therefore the userspace part... I think you get the point.
Also, if the userspace part writes it data to the filesystem, it would
increase the memory pressure even further by causing new blocks to be
added to the cache.
Is there anything one could do to prevent this from happening (besides
from praying that there is always enough free memory)?
I'm just starting with kernel stuff, so this might as well a stupid
question. I've tried to find something in the archives, but with no
result.
Thanks for you answers.
Rolf
reply other threads:[~2002-03-23 1:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1016844254.1193.31.camel@desktop \
--to=mail@rschaeuble.de \
--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