public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* Block device driver in user space
@ 2002-03-23  0:44 Rolf Schäuble
  0 siblings, 0 replies; only message in thread
From: Rolf Schäuble @ 2002-03-23  0:44 UTC (permalink / raw)
  To: linux-kernel

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


^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2002-03-23  1:15 UTC | newest]

Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-03-23  0:44 Block device driver in user space Rolf Schäuble

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox