Re: close and ERESTART

2011-12-26 Thread Matthew Mondor
On Mon, 26 Dec 2011 05:19:22 + Taylor R Campbell campbell+net...@mumble.net wrote: + + error = fd_close(SCARG(uap, fd)); + if (error == ERESTART) + error = EINTR; + + return error; If it's also guaranteed that the file descriptor state is closed in the event of

Re: raidframe rebuild question

2011-12-26 Thread Edgar Fuß
What's the right way to do this? What about creating a (Level 1) raid13 consisting of wd3e, adding (a partition on) that as a spare to raid0, and failing raid0's raid11e component?

Re: raidframe rebuild question

2011-12-26 Thread Mouse
[raidframe woes] What's the right way to do this? What about creating a (Level 1) raid13 consisting of wd3e, adding (a partition on) that as a spare to raid0, and failing raid0's raid11e component? That's probably what I should have done. I don't seem able to do it now, though; raidctl -r

Re: Network drivers and memory allocation in interrupt context

2011-12-26 Thread Sverre Froyen
On On 2011-12-08 at 21:03 David Young wrote On Thu, Dec 08, 2011 at 07:06:29PM -0700, Sverre Froyen wrote: Hi, I now have a semi-working pool_cache based memory allocator for network drivers (tested using the iwn driver). I am uncertain, however, about how to get it fully functioning.

Re: fifo and [acm]time

2011-12-26 Thread Mouse
The only value I can see in the [acm]time of either a FIFO or an AF_LOCAL socket file is to see when the relevant software last did anything with it. Diagnostic information is useful, but is it useful to store on disk? In many cases storing it in core is good enough, though I'm sure there are

Re: fifo and [acm]time

2011-12-26 Thread Taylor R Campbell
Date: Mon, 26 Dec 2011 18:35:34 + From: Mouse mo...@rodents-montreal.org Is one inode update per minute enough to be a significant issue? It means the disk must continue spinning and, e.g., will continue to draw power from a laptop battery to do so, even when the system is

Re: raidframe rebuild question

2011-12-26 Thread matthew green
i seem to recall that we found some missing close calls inside raidframe that are now fixed in -current, and possibly pulled upto netbsd-5 and probably not netbsd-4? i think you do need a reboot, unfortunately. .mrg.

Re: raidframe rebuild question

2011-12-26 Thread Mouse
i seem to recall that we found some missing close calls inside raidframe that are now fixed in -current, and possibly pulled upto netbsd-5 and probably not netbsd-4? Worse than that - see below. i think you do need a reboot, unfortunately. I think so too. I finally got around to looking at