[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
On Sun, Nov 17, 2013 at 10:33:43AM +0100, Emmanuel Dreyfus wrote:
> > To answer both you and the Mouse - the difference is that a user process
> > actually writing data consumes measurable resources, and thus is easy to
> > find and kill. When everything happens in the kernel, spotting which
> > arrantly idle user process is making it happen is not at all easy.
> We could fork a kernel thread that would go to userspace to do the work
> with a write() loop, with appropriate credentials. Does it makes sense?
I do not think that makes the slightest sense. Also if you really want
FALLOC_FL_KEEP_SIZE, it won't be adequate.
David A. Holland
Main Index |
Thread Index |