[ENBD] two questions
Peter T. Breuer
ptb@it.uc3m.es
Thu, 15 Feb 2001 04:55:00 +0100 (MET)
"A month of sundays ago Peter T. Breuer wrote:"
> The problem with the default is that it does unplugging on the disk
> taskqueue, which is dangerous. The commented call in init_module
> installs an unplugging function that does unplugging on the scheduler
> taskqueue instead. But that seemed to stick when I tried it. Unplugging
> on the scheduler should give time for the userspace daemon to run.
I should add that there is a special unplugging function in the nbd
code that can be used to do the unplugging, but I haven't really
discovered how to implant it correctly in the 2.4 kernel yet.
(or the problem may be that it is implanted, and shouldn't be).
These aspects of working with the 2.4 kernel are in shakedown mode. I
am only trying to get basic functionality up. I believe the driver just
passed some basic read and write regression tests. It was hard to get
it to that point.
> > /proc/nbdinfo'.
> > Is it right? But it seems that mergeing help nothing. I used iozone to
You need a "echo -n merge_requests=1 > /dev/proc_nbdinfo". The -n is
important. I don't know if the /proc write mechanism is working in
kernel 2.4, btw!
> It used to cause horrible death in 2.2. Has it stopped doing that?
Peter