As I understand, at VFS level, VOP_STRATEGY(9) is used for I/O to block
devices. Where does that name comes from?
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org
On Sun 16 Oct 2011 at 00:52:35 +0100, Mindaugas Rasiukevicius wrote:
David Young dyo...@pobox.com wrote:
This isn't just a lint bug? At least two of these are instances of void
functions returning the return value of a void function, for which
the compiler need neither throw away a value
On Tue, 18 Oct 2011, Emmanuel Dreyfus wrote:
As I understand, at VFS level, VOP_STRATEGY(9) is used for I/O to block
devices. Where does that name comes from?
Block devices use the `strategy()' routines to schedule operations
because, unlike character devices which typically immediately post
We could use the reference counter in struct cfdriver to keep driver
modules busy, but I'm not sure if the system can figure out what's
unneeded if a needed driver might be one for a hotpluggable device.
Would you treat those drivers differently? What about drivers (if_ath_pci
comes to mind)
Emmanuel Dreyfus m...@netbsd.org wrote:
When running perfused stress test (a build of NetBSD over a glusterfs
volume), memory gets low, and the machine hangs.
I made some progress, thanks to Manuel Bouyer suggestions. There are
code paths where pagedaemon sleeps for memory. During my tests, I
On Tue, Oct 18, 2011 at 11:28:22AM -0400, Jared McNeill wrote:
I played around with driver module autoloading a while back, and it
worked pretty well but the implementation I came up with required
duplicating match data in module.plist.
This sounds like a step in the right direction (recording
I think you'd just need to find a way to supply that data for built-in
modules too.
On Tue, 18 Oct 2011, David Young wrote:
On Tue, Oct 18, 2011 at 11:28:22AM -0400, Jared McNeill wrote:
I played around with driver module autoloading a while back, and it
worked pretty well but the
# David Young 2011-10-18:
On Tue, Oct 18, 2011 at 11:28:22AM -0400, Jared McNeill wrote:
I played around with driver module autoloading a while back, and it
worked pretty well but the implementation I came up with required
duplicating match data in module.plist.
This sounds like a step
On Tue, Oct 18, 2011 at 12:50:58PM -0400, Jachym Holecek wrote:
# David Young 2011-10-18:
On Tue, Oct 18, 2011 at 11:28:22AM -0400, Jared McNeill wrote:
I played around with driver module autoloading a while back, and it
worked pretty well but the implementation I came up with required
On Tue, Oct 18, 2011 at 10:05:24AM -0700, Hisashi T Fujinaka wrote:
I'm sorry I wasn't paying attention to this earlier. I've seen reboots
on my amd64 netbsd-5 server under probably heavy load (building
userspace or rebuilding all my pkgsrc packages, for example) but haven't
seen a core file
Hisashi T Fujinaka ht...@twofifty.com wrote:
I'm sorry I wasn't paying attention to this earlier. I've seen reboots
on my amd64 netbsd-5 server under probably heavy load (building
userspace or rebuilding all my pkgsrc packages, for example) but haven't
seen a core file (I probably disabled
11 matches
Mail list logo
