On Sun, 28 Sep 2003, Poul-Henning Kamp wrote:
Basically:
1. Do not call makedev().
2. If you do cloning, please look at the patches I posted
for if_tun/if_tap for how to do it.
show an actual document please, explaining how this works from the
user's POV..
I am in the process of adding ref-counting and locking to dev_t,
and would very much prefer if we could get this step completed
soon before 5-STABLE gets branched.
All this will be transparent to the majority of device drivers, as
the refcounting will happen in the make_dev() and destroy_dev()
On Sunday, 28 September 2003 at 23:22:07 +0200, Poul-Henning Kamp wrote:
Basically:
3. If you do a normal device driver, cache the result
from when you call make_dev().
...
./dev/vinum
Failure to cache result of make_dev() ?
Where should this be cached?
On Sun, Sep 28, 2003 at 11:22:07PM +0200, Poul-Henning Kamp wrote:
I am in the process of adding ref-counting and locking to dev_t,
and would very much prefer if we could get this step completed
soon before 5-STABLE gets branched.
All this will be transparent to the majority of device
On Mon, 29 Sep 2003, Greg 'groggy' Lehey wrote:
On Sunday, 28 September 2003 at 23:22:07 +0200, Poul-Henning Kamp wrote:
Basically:
3. If you do a normal device driver, cache the result
from when you call make_dev().
...
./dev/vinum
Failure to cache
On Sunday, 28 September 2003 at 19:46:20 -0400, Robert Watson wrote:
On Mon, 29 Sep 2003, Greg 'groggy' Lehey wrote:
On Sunday, 28 September 2003 at 23:22:07 +0200, Poul-Henning Kamp wrote:
Basically:
3. If you do a normal device driver, cache the result
from when you call
In message [EMAIL PROTECTED], Greg 'groggy' Lehey
writes:
--yRA+Bmk8aPhU85Qt
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Sunday, 28 September 2003 at 23:22:07 +0200, Poul-Henning Kamp wrote:
Basically:
3. If you do a normal device driver, cache the result
