KGDB, serial ports, and MP

I've run into the bug described at: http://mail-index.netbsd.org/netbsd-bugs/2010/03/17/msg016596.html and the proposed fix (splserial) seems to work. This is on an amd64 VM; we'll try a physical (multi-cpu) machine as well. Reading the various messages, I get the impression that KGDB on MP

Re: KGDB, serial ports, and MP

The comment was made when I proposed that fix is that it will NOT handle the MP case because splserial() doesn't affect other CPUs. And one of the commenters pointed me to places to look for how to do the MP part. Thanks - that makes sense. I haven't done that yet; it's on my to-do

Re: why not remove AF_LOCAL sockets on last close?

Can anyone tell me why, exactly, we shouldn't remove bound AF_LOCAL sockets from the filesystem on last close? The following test program produces second socket bind failed on every system I've tested it on, and seems to cover the only possible use case for this feature... Have you

Re: why not remove AF_LOCAL sockets on last close?

Thor Simon t...@coyotepoint.com writes: On Fri, Jun 25, 2010 at 08:47:49AM -0400, Greg Troxel wrote: Can anyone tell me why, exactly, we shouldn't remove bound AF_LOCAL sockets from the filesystem on last close? The following test program produces second socket bind failed on every

Re: netbsd-5.1_RC3 crash at Dell M710

6b...@6bone.informatik.uni-leipzig.de writes: On Fri, 13 Aug 2010, Jean-Yves Migeon wrote: Date: Fri, 13 Aug 2010 17:03:14 +0200 From: Jean-Yves Migeon jeanyves.mig...@free.fr To: 6b...@6bone.informatik.uni-leipzig.de Cc: tech-kern@netbsd.org Subject: Re: netbsd-5.1_RC3 crash at Dell M710

Re: SLIP coexisting with serial data?

der Mouse mo...@rodents-montreal.org writes: I was thinking of making this another protocol type, akin to what I mentioned (probably on tech-net) back in '02 - I just now (finally) filed kern/43959 containing patches to support v6 as well as v4, something that's easy compared to making the

Re: SLIP coexisting with serial data?

der Mouse mo...@rodents-montreal.org writes: I have a situation in which it would be useful to run SLIP on a serial console. [...] Given how rare the situation is, maybe it's best to do the encapsulation/decapsulation in user mode, and feed into SLIP via a pty. (I also suspect that the

Re: Heads up: moving some uvmexp stat to being per-cpu

I have a fairly large but mostly simple patch which changes the stats collected in uvmexp for faults, intrs, softs, syscalls, and traps from 32 bit to 64 bits and puts them in cpu_data (in cpu_info). This makes more accurate and a little cheaper to update on 64bit systems. I hvaen't

Re: freebsd 5.99.41 as XEN3_DOMU

Manuel Bouyer bou...@antioche.eu.org writes: Well, in the current state, modules are a not enabled in the Xen kernels (modules should be built specifically for Xen, but the build tools do not allow this right now). So you have to compile all what you need in a monolitic kernel. But ZFS is

Re: Problems with TCP Window size under NetBSD-5???

Check out pkgsrc/graphics/xplot, and $ tcpdump -r tracfile -S -tt | tcpdump2xplot $ xplot foo.xplot and read the README files in the sources. Without doing this, or reinventing it, you are unlikely to understand what TCP is doing. If you would like to put up a raw tcpdump (-w, capturing the

Re: extend sysmon watchdog modes?

I am seeing a need for a new watchdog mode that is similar to WDOG_MODE_KTICKLE but instead of the watchdog service function running from a callout it needs to run from a (higher level) hardware interrupt. I don't understand the use case. I am running watchdogs in user tickle, and

Re: link(2) on a symlink to a directory fails

Emmanuel Dreyfus m...@netbsd.org writes: I was trying to track down a bug in glusterfs on NetBSD and encountered a behavior difference between NetBSD and Linux. NetBSD will refuse (EPERM) to link(2) on a symlink to a directory, while Linux is fine with such an operation (but fails to link(2)

Re: Adding linux_link(2) system call

Steven Bellovin s...@cs.columbia.edu writes: Consider the following two sequences: a) Create a file A b) Create a symlink X-A c) Create a hard link Y=X d) Unlink a e) Create a directory A or a) Create a symlink X-A', where A' doesn't exist b)

Re: nfs_lookup() panic, again

I'm not David, but: I would also suggest tcpdumping to a file the nfs traffic, on some other machine (perhaps the osx box) and then when the panic happens look at the last few transactions to see if you spot anything odd. There's a cache of name translations (used for namei), maintained by

fsync, rdiff-backup, wapbl, and WD Elements 1T drive

netbsd-5, i386, 2 x 400G SATA in rf RAID1, external USB2 WD Elements 1T I have a UFS2+WAPBL filesystem on the above RAID1 with ~900K files in ~320GB. I'm backing it up with rdiff-backup to a USB2 external disk. The external disk has a single large UFS2+WAPBL partition. I found that backups

Re: fsync, rdiff-backup, wapbl, and WD Elements 1T drive

Thanks for the comments. This is rdiff-backup, not rsync, and it has the notion of considering the modified mirror dirty until it finishes, and it will roll back on restart. I am not clear how well it does about verifying contents (or timestamps before the last full-backup timestamp?). I am

Re: fsync, rdiff-backup, wapbl, and WD Elements 1T drive

chris...@astron.com (Christos Zoulas) writes: In article 20010318.pa13ihod001...@ginseng.pulsar-zone.net, Matthew Mondor mm_li...@pulsar-zone.net wrote: On Mon, 31 Oct 2011 19:58:27 -0400 Greg Troxel g...@ir.bbn.com wrote: Obligatory actual netbsd tech-kern content: It seems like we

Re: Lost file-system story

Interesting situation. I agree that after 30s to a minute that most things should have been flushed. As a side note, it would be interesting to benchmark async vs wapbl. I have never really looked, but it has always seemed that it would be nice to have: statistics visibility into the number

Re: Lost file-system story

Andy Ruhl acr...@gmail.com writes: If solving your problem depends on sync frequency, I don't see why this shouldn't be managed by some knob to twiddle. Given that the crash scenario doesn't get worse depending on where the knob is or if the crash happens while the knob is working. If it

Re: Lost file-system story

Greg A. Woods wo...@planix.ca writes: At Mon, 12 Dec 2011 14:23:40 -0600, Eric Haszlakiewicz e...@nimenees.com wrote: Subject: Re: Lost file-system story Donald, don't listen to Greg. Just in case it needs to be repeated, you're not the only one that thinks it is reasonable to expect a

Re: heads-up: IPSEC is now FAST_IPSEC

Mindaugas Rasiukevicius rm...@netbsd.org writes: Matthias Drochner m.droch...@fz-juelich.de wrote: I've just made FAST_IPSEC the default implementation which gets used if the IPSEC kernel option is present. ... The old KAME implementation is still available through the KAME_IPSEC

Re: Snapshots in tmpfs

Another possible thing to do (instead) would be to look at Coda, and consider something like porting Coda to use FUSE instead of a homegrown (pre-FUSE, to be fair) kernel module. A bigger challenge is to separate the write-back caching from the upstream server protocol, so that one could use

Re: Issues using KGDB on a Linux machine to debug NetBSD

For what it's worth, some of my colleagues are successfully using the gdb from netbsd-5 (and I'm 99% sure netbsd-6) with the corresponding systems (all i386) on serial ports. Your output reports make me wonder if gdb changed the protocol. I'd look at the gdb 7 sources to see if there is an

Re: selectively disabling atime updates?

Thor Lancelot Simon t...@panix.com writes: On Mon, Jun 11, 2012 at 05:52:27PM +0200, Edgar Fu? wrote: Yes, but I have to question whether and why it would improve performance in this case. The stream of atime updates is still happening on the underlying filesystem, and that is still

leapseconds and special-purpose code

I've heard a lot of incoherent things about Linux and leapsecond problems. Here's something coherent: http://landslidecoding.blogspot.com/2012/07/linuxs-leap-second-deadlocks.html I have a NetBSD system with a GPS timing receiver running as NTP stratrum 1, and had set up the leap second file

Re: pinning down dk? assignment

Martin Husemann mar...@duskware.de writes: On Mon, Jul 23, 2012 at 04:17:21PM +0200, Edgar Fuß wrote: Can I somehow pin down which dk? gets assigned to which GPT partition? You can mount them by name. I have (on my non-GPT root disk): NAME=sb2k5Root/a/ ffs rw,log

Re: Raidframe and disk strategy

Thor Lancelot Simon t...@panix.com writes: On Wed, Aug 08, 2012 at 03:07:24PM -0700, Brian Buhrow wrote: Presumably, the underlying disks can use what ever strategy they use for handling queued data, but I'm wondering if there is a particular reason the fcfs strategy was chosen for the

Re: Raidframe and disk strategy

Thor Lancelot Simon t...@panix.com writes: On Thu, Aug 09, 2012 at 08:40:51AM -0400, Greg Troxel wrote: Thor Lancelot Simon t...@panix.com writes: RAIDframe implements its own disk sorting algorithm (several, actually) internally. Why sort twice? I don't follow

Re: WAPBL/cache flush and mfi(4)

It seems that after issuing a cache flush we should hold operations that write new data until the cache flush is complete. Also, it seems like flush is a big hammer and we really want to ask that all writes before a barrier be done instead. But I'm unclear on the details. I've seen problems

Re: cprng sysctl: WARNING pseudorandom rekeying.

FWIW, I agree with the notion that defaults should be at a path that is ~always in root; it's normal to have /var in a separate fileystem (at least for old-school UNIX types; I realize the kids these days think there should be one whole-disk fs as /). pgpIxpye42BeB.pgp Description: PGP

Re: [PATCH] POSIX extended API set 2

I want the names to follow a clear and easily-documented pattern. However, I also want the inconsistent POSIX names to be provided. I see where you're coming from, but it seems like asking for trouble to encourage any code to be written which uses function names other than the ones defined

Re: Problem identified: WAPL/RAIDframe performance problems

Edgar Fuß e...@math.uni-bonn.de writes: I seem to be facing two problems: 1. A certain svn update command is ridicously slow on my to-be file server. 2. During the svn update, the machine partially locks up and fails to respond to NFS requests. Thanks to very kind help by hannken@,

Re: Broadcast traffic on vlans leaks into the parent interface on NetBSD-5.1

Brian Buhrow buh...@nfbcal.org writes: Hello. I've just noticed an issue where broadcast traffic on vlans also shows up on the parent interface. My environment is NetBSD-5.1/i386 with the wm(4) driver. I'm not sure yet if the problem is specific to the wm(4) driver or if it's a more

Re: Broadcast traffic on vlans leaks into the parent interface on NetBSD-5.1

dhcpd, last I checked, used bpf and not sockets. If dhcpd is bpf, I would suggest reading the bpf_tap calls in the driver. It could be that if_wm.c has a spurious on. If it's not, I don't know what's going on. pgpQRa4Ge4oOR.pgp Description: PGP signature

Re: Broadcast traffic on vlans leaks into the parent interface on NetBSD-5.1

Brian Buhrow buh...@nfbcal.org writes: However, some drivers, i.e. stge(4), send the packet to the bpf engine after step 2, above, before performing steps 3, 4 and 6. Without having tested anything yet, this seems more correct to me. I will try to get a test environment together with

Re: Broadcast traffic on vlans leaks into the parent interface on NetBSD-5.1

Roy Marples r...@marples.name writes: On 05/12/2012 8:39, David Laight wrote: Although DHCP has to do strange things in order to acquire the original lease, renewing it should really only requires packets with the current IP address. It's not strange, it's very well documented in RFC2131.

Re: Broadcast traffic on vlans leaks into the parent interface on NetBSD-5.1

jnem...@victoria.tc.ca (John Nemeth) writes: On Apr 27, 3:15am, David Laight wrote: } On Tue, Dec 04, 2012 at 10:17:23PM -0800, John Nemeth wrote: } } We use ISC's DHCP server. As third party software, it is designed } to be portable to many systems. BPF is a fairly portable

Re: MI boot args revamp?

I would like to have a way to pass a string composed of the same flags (we can continue to use our existing -a, -s and other flags) in a consistent manner from one platform to another, to be able to adjust driver options, kernel options, whatever, and to be able to expect it to be

Re: Fstrans rewrite without rwlock

J. Hannken-Illjes hann...@eis.cs.tu-bs.de writes: Attached is a complete rewrite based on passive serialization and condvars. The fast paths (fstrans_start/fstrans_done on a file system not suspended or suspending and fscow_run) now run without locks or other atomic operations. Suspension

rump locking fix

We have been using rump a) in a system compiled with debugging and b) with IPsec. I have several changes, all due to Mark Keaton of BBN, which I'll send here, and commit if there are no objections. When compiling debug versions of the stock NetBSD 6

Re: What's an MPSAFE driver need to do?

Mouse mo...@rodents-montreal.org writes: dholland says that a driver is MPSAFE if it does not require kernel_lock to work correctly. What's kernel_lock? man -k turns up nothing; some grepping leads me to think it's what I've seen called on the lists a `giantlock', which is what I thought

Re: netbsd-6: pagedaemon freeze when low on memory

That patch makes sense, but it seems like the infinite loop is a separate bug, regardless. pgpTuUkwCl6SM.pgp Description: PGP signature

Re: vmem(9) (was Re: netbsd-6: pagedaemon freeze when low on memory)

[discussion of pagedaemon having a tight loop when kmem is low but trying to free some isn't successful] http://mail-index.netbsd.org/tech-kern/2013/03/04/msg015063.html Lars has adjusted the default maxvnodes, which should help most people From avoiding the pagedaemon tight loop. But I

Re: vmem(9) (was Re: netbsd-6: pagedaemon freeze when low on memory)

Lars Heidieker l...@heidieker.de writes: One problem I see with the patch is, if applied the pagedaemon gives up pool_draining after the first call to pool_drain that doesn't free anything. pool_drain drains one and only one pool per call, so chance are good that we stop to early. (I

Re: vmem(9) (was Re: netbsd-6: pagedaemon freeze when low on memory)

Lars Heidieker l...@heidieker.de writes: On 2013-03-19 02:11, Greg Troxel wrote: How hard do you think it would be to make pool_drain() keep trying pools until one succeeded in freeing something (or it tried them all)? Do you see any downside in that change? It seems like it's just

Re: Question about pool(9) sizes

Brian Buhrow buh...@nfbcal.org writes: Hello. In my continuing quest to try and get i/o performance up on some NetBSD-5.1 production boxes I have, I find I have a question about the minimum and maximum sizes of a specific pool. Given the following snippet of output from vmstat -m,

Re: high load, no bottleneck

Edgar Fuß e...@math.uni-bonn.de writes: I myself can't make sense out of the combination of -- vfs.wapbl.flush_disk_cache=0 mitigating the problem -- neither the RAID set nor its components showing busy in iostat Maybe during a flush, the discs are not regarded busy? Do you have physical

Re: kernel_lock prememption

Rohan Akela rohanak...@gmail.com writes: I would like to know if a thread holding kernel_lock which is a spinlock can be preempted or not ? The implementation of kernel_lock in kern_lock.c seems to suggests that it can be preempted because the it uses splvm which implies IPL_VM. So a

Re: zero-length symlinks

David Holland dholland-t...@netbsd.org writes: rmind@ points out that it's possible to create zero-length symlinks. As zero-length symlinks aren't sensible, this should probably be prohibited. Does anyone see any reason they shouldn't be? What does POSIX say? I note that one can't creaet a

Re: pulse-per-second API status

This patch to netbsd-5 adds pps support to ucom(4), which should enable pps on all usb serial chips that report modem control changes. It's entirely cut/paste from com(4) except that MSR_DCD became UMSR_DCD. I have tested it with a GR301-W and the in-tree (-5) ntpd. I am seeing offsets of

Re: pulse-per-second API status

Mouse mo...@rodents-montreal.org writes: I now think the 100ms was due to the wrong polarity on the pps signal From this device. After fixing that, I'm seeing times that are within 5 ms (well within expected network asymmetry), and currently the jitter is 0.169 ms. (I still need to figure out

Re: pulse-per-second API status

Thanks for the comments. Terry Moore t...@mcci.com writes: USB is not a very good way to do PPS synchronization if you're looking for usec resolution -- there are huge and unpredictable delays that can be introduced from a number of sources. Agreed, but that's not the question on the table.

Re: pulse-per-second API status

I don't know this API. But my first reaction when I saw the designation PPS is to think of GPS timekeeping boxes and other precision frequency sources that have a PPS output. On those devices, the PPS output is divided down from the main oscillator frequency, i.e., you can expect

Re: pulse-per-second API status

Terry Moore t...@mcci.com writes: If the time info is presented into NTP using the same interface that network packets use, then jitter will be pretty well damped (and will be less, in any case, than typical network packet transport jitter). It is totally an application question as to

Re: Vnode API change: add global vnode cache

Mindaugas Rasiukevicius rm...@netbsd.org writes: Taylor R Campbell campbell+netbsd-tech-k...@mumble.net wrote: Date: Mon, 7 Apr 2014 16:56:58 +0100 From: Mindaugas Rasiukevicius rm...@netbsd.org What is intern? `Intern' means `lookup, or create and insert if not there'. The

Re: Inconsistency with COMPAT_10

Maxime Villard m...@m00nbsd.net writes: COMPAT_10 should be added in netbsd32, or removed from the native syscall. But I'm not sure which fix should be applied. Probably added in compat32. But I don't know how common programs are that rely on this bug. I wonder if pathbuf_create results in

Re: cprng_fast implementation benchmarks

After reading all these messages a bit too fast, it seems to be that we can add to Thor's analysis Moving the fast-not-super-strong PRNG to ChaCha8 is clearly a step forward from what we have now. (really this is his conclusion) It remains for Someone to do more formal work (perhaps in

Re: connect() returns EACCES

m...@netbsd.org (Emmanuel Dreyfus) writes: Before I start adding printf in the kernel, anyone has an idea why connect() on an AF_INET socket can return EACCES? firewall code can return permission denied pgpce7uTJxvzN.pgp Description: PGP signature

Re: API/ABI rank of headers in /usr/include/isofs/cd9660

while fixing rollovers and implementing a new mount_cd9660 option -s, i stumble over the content of public include directory /usr/include/isofs/cd9660 which exposes all header files from the kernel source of cd9660: cd9660_extern.h cd9660_rrip.h iso_rrip.h

Re: API/ABI rank of headers in /usr/include/isofs/cd9660

Thomas Schmitt scdbac...@gmx.net writes: I think Greg is right - historic accident. They are quite up to date. Sure. It's accidental that so much is exposed, but part of the build system that they are copied. Is the mechanism known by which /usr/src/sys/fs/cd9660/*.h gets forwarded to

Re: API/ABI rank of headers in /usr/include/isofs/cd9660

Thomas Schmitt scdbac...@gmx.net writes: You can certainly drop them in the Makeefile in your source tree and do a build and see what happens. My builds can hardly have installed or overwritten them. cd9660_extern.h differs between /usr/include and /usr/src. The files in /usr/include are

Re: API/ABI rank of headers in /usr/include/isofs/cd9660

Thomas Schmitt scdbac...@gmx.net writes: Hi, get rid of OBJDIR and DESTDIR Where would these be, if present ? (I checked env and cd9660/Makefile.) They would be under /usr/obj after you run build.sh. run a full build (from build.sh; see pkgsrc/sysutils/etcmanage:BUILD-NetBSD for

Re: msdosfs and small sectors

Maxime Villard m...@m00nbsd.net writes: Le 15/07/2014 17:57, Martin Husemann a écrit : On Tue, Jul 15, 2014 at 03:27:08PM +0200, Maxime Villard wrote: 'secsize' is retrieved through getdisksize(), via an ioctl on the device. force it to be 512 bytes minimum? Martin I thought about

Re: msdosfs and small sectors

Maxime Villard m...@m00nbsd.net writes: Le 17/07/2014 06:01, matthew green a écrit : + if (secsize DEV_BSIZE) { +#ifdef DIAGNOSTIC + printf(Invalid block secsize %d\n, secsize); +#endif + error = EINVAL; + goto error_exit; + } if (argp-flags

Re: icache sync private rump component

Alexander Nasonov al...@yandex.ru writes: I'd like to commit a private rump component that adds a hypercall for synching icache. This will help us to test bpfjit and npf on arm and mips platforms. Why is this private? If it's generally necessary, it should become part of the standard

Re: icache sync private rump component

Alexander Nasonov al...@yandex.ru writes: Greg Troxel wrote: Why is this private? If it's generally necessary, it should become part of the standard interface.Is it just that sljit is the only place that is currently creating code that is later executed? I made a change

Re: CVS commit: src/sys/kern

Maxime Villard m...@netbsd.org writes: Module Name: src Committed By: maxv Date: Tue Jul 22 07:38:41 UTC 2014 Modified Files: src/sys/kern: subr_kmem.c Log Message: Enable KMEM_REDZONE on DIAGNOSTIC. It will try to catch overflows. No comment on tech-kern@ I didn't see

Re: CVS commit: src/sys/kern

Nick Hudson sk...@netbsd.org writes: On 07/22/14 12:49, Greg Troxel wrote: Maxime Villard m...@netbsd.org writes: Module Name:src Committed By: maxv Date: Tue Jul 22 07:38:41 UTC 2014 Modified Files: src/sys/kern: subr_kmem.c Log Message: Enable

Re: CVS commit: src/sys/kern

I realized that two things can be separated. One is whether DIAGNOSTIC turns on features that increase the size of memory allocations, which is my real concern. The other is whether the KMEM_SIZE and KMEM_REDZONE should be on by default in -current on various architectures, which is I think

Re: Making bpf MPSAFE (was Re: struct ifnet and ifaddr handling ...)

Ryota Ozaki ozak...@netbsd.org writes: BTW, I worry about there is no easy way to know if a function in a critical section blocks/sleeps or not. So I wrote a patch to detect that: http://www.netbsd.org/~ozaki-r/debug-pserialize.diff Is it meaningful? It seems sensible, but it is very much

Re: tmpfs projects

Nick nicky1...@gmail.com writes: Hello, I am new to NetBSD and would like to see if there is any chance that I could find something related to file system to work on (I am working on networking/platform SW full-time) Are these two projects already complete or been taken care of by people?

Re: FFS: wrong superblock check ~ crash

Manuel Bouyer bou...@antioche.eu.org writes: On Mon, Oct 20, 2014 at 03:58:45PM +, Taylor R Campbell wrote: Date: Mon, 20 Oct 2014 17:46:06 +0200 From: Manuel Bouyer bou...@antioche.eu.org Sure. There's lot of other ways to crash the kernel with a broken ffs. In this

Re: FFS: wrong superblock check ~ crash

Martin Husemann mar...@duskware.de writes: On Mon, Oct 20, 2014 at 07:48:31PM +0100, Mindaugas Rasiukevicius wrote: Perhaps we can debate what to do with corrupted / when the system is booting, but for other cases (especially hot-plug or external disks) I certainly do not expect a crash.

Re: if_wm between netbsd-6 and netbsd-7 issue

I don't know what broke between 6 and 7, but in both -5 and -6 I have observed hangs when all one of those is pushed hard, to the point that we removed the cards. I suspect, but cannot prove, that the problem is the ppb on the 4-port card. pgpOQwBDPtZiv.pgp Description: PGP signature

OpenZFS?

notion of heading to OpenZFS makes sense, and how hard it is likely to be. -- Greg Troxel g...@ir.bbn.com pgpt_7XjbsCzk.pgp Description: PGP signature

Re: fs/ headers

Maxime Villard m...@m00nbsd.net writes: most of the FSs under sys/fs have their headers in /usr/include/fs/FS-NAME/. Some are just in /usr/include/FS-NAME/: msdosfs - adosfs - filecorefs - ntfs. Is it intentional? It's ok if I move them in fs/? Are any of them public APIs, or just used by a

Re: Making dhcpcd work on diskless clients

Roy Marples r...@marples.name writes: I don't fully understand what you are saying. But do you have an idea of how this can be fixed then without dhcpcd having to learn the routing table at load time? It seems to me that on a diskless client, the only really sound approach is to ensure that

Re: Making dhcpcd work on diskless clients

Roy Marples r...@marples.name writes: The last time I tried using RTM_CHANGE, it did not clear the learned cloned routes which RTM_DELETE handily does for me. This is important if we need to move a subnet route from one interface to another. That seems like a bug in RTM_CHANGE. But the case

Re: Removal of compat-FreeBSD

Maxime Villard m...@m00nbsd.net writes: Apparently, compat-FreeBSD is needed by tw_cli users. Therefore I think I will just disable it by default in the GENERIC kernels, unless anyone disagrees. Our norms for significant changes are more or less about consensus or preponderance of opinion.

Re: CVS commit: src/sys/dev

(moved to tech-kern, becuase source-changes-d is too buried and this is only happening there because it's post-commit discussion rather than pre-commit review) Michael van Elst mlel...@serpens.de writes: On Tue, May 05, 2015 at 07:47:09PM -0400, Greg Troxel wrote: Michael van Elst mlel

Re: (patch) Improved documentation and examples of dynamic modules

Kamil Rytarowski n...@gmx.com writes: Also, happy doesn't seem like a useful name; examples should have names that suggest the kinds of things they do with respect to the module system, to guide people choosing which ones to read. Well, I like /dev/happy for Happy Number generator. What

Re: (patch) Improved documentation and examples of dynamic modules

I don't think examples of kernel source code belong in /usr/share/examples. That's for example config etc. to use with programs that are part of NetBSD; this is about extending the system by writing code rather than using the system. I think an example module belongs in the source tree as a

Re: (patch) Improved documentation and examples of dynamic modules

Kamil Rytarowski n...@gmx.com writes: Paul Goyette wrote: The happy module makes a claim that 4 digit numbers cannot cycle, and uses a cache[] table for all numbers below 1000. Can you please provide a reference to back up the cannot cycle claim? :) And please initialize (or

Re: bottom half

Taylor R Campbell campb...@mumble.net writes: What I meant when I said that to Kamil is that we don't have any formalized notion called `top half' and `bottom half'. We have hard interrupt handlers which are supposed to have small bounded latency, and we have soft interrupt handlers and

Re: KGDB/i386 broken/supposed to work?

I am a bit fuzzy on the details, but definitely in 2010 on netbsd-5 remote kgdb on i386 worked. I am 95% sure it still worked on netbsd-6 in 2011/2012. pgpCcJa1jGgY9.pgp Description: PGP signature

Re: Partitioning schemes

Reinoud Zandijk rein...@netbsd.org writes: We have amongs others, MBR, GPT, disklabels, (sun-)disklabels, LVM, RAID etc.etc. The current idea is to have wedge discovery creating wedges for each type. Not my favorite but it usually kind of works. Some of those are to be compatible with other

Re: FFSv1 fails check in -current

Reinoud Zandijk rein...@netbsd.org writes: when trying to update my NAS to -current, or at least to a -current kernel, my FS failed to mount. It reported: wd0 at atabus1 drive 0 wd0: Hitachi HDS721010CLA332 wd0: 931 GB, 1938021 cyl, 16 head, 63 sec, 512 bytes/sect x 1953525168 sectors

Re: Raidframe low I/O for parity rebuild, but when accessed through rraid* devices

mlel...@serpens.de (Michael van Elst) writes: jeanyves.mig...@free.fr (Jean-Yves Migeon) writes: [...] the first few minutes of the parity rebuild go fine, both disks working at about 20-25MiB/s (which is their nominal speed when used in !raid setup). But after that, the rebuild I/Os slow to

Re: [PATCH] Fixing soft NFS umount -f, round 1

m...@netbsd.org (Emmanuel Dreyfus) writes: The intent of hard mount is to make sure any I/O completes, at the expense of waiting a long time if the server is down. But I think it is wrong to extend that up to prevent root from forcibly unmounting a filesystem. But thenthe problem is that

Re: spl question

Maxime Villard m...@m00nbsd.net writes: What happens if the kernel calls splx(s) twice? And what happens if it forgets to call splx(s)? Like: s = splnet(); [...] NOT RELATED TO S return; NO SPLX(S) splx(s) twice (with the same s, saved from a single splnet) is

Re: Potential problem with reading data from usb devices with ugen(4)

Brian Buhrow writes: > Hello. Another question about the read ahead and write behind code > in ugen(4). It seems that if a write call comes in with a block of data, > and a second write call comes in with a second block of data before the > first block of data has

Re: Anomalies while handling p_nstopchild count

Paul Goyette writes: > Looks like not much has happened here, and all four patches apply > cleanly to > > netbsd-7 > netbsd-6 > netbsd-6-0 > netbsd-6-1 > > IMHO, pull-up to netbsd-6 makes sense, but I'm not sure if we would want > to change things

Re: Potential problem with reading data from usb devices with ugen(4)

Brian Buhrow writes: > hello. In looking further at the ugen(4) driver, it looks like there > has been some effort to get things like select/poll(2) working with ugen(4) > connected devices, as well as having read calls return after a specific > timeout interval.

Re: Potential problem with reading data from usb devices with ugen(4)

[ugen bulk read ahead code] This code was written under my direction back in 2006 to support the specific use case of the USRP with GNU radio. The only reason it's needed is to get better pipelining to get closer to the max transfer speeds. So: are you doing something where not using

Re: Potential problem with reading data from usb devices with ugen(4)

Given that you want short reads, why are you setting read ahead? Are you failing to get enough throughput without it? pgprITHBwCeBl.pgp Description: PGP signature

Re: Potential problem with reading data from usb devices with ugen(4)

Brian Buhrow writes: > hello. I don't necessarily need the read ahead functionality, though > it might be useful when I start doing large transfers to and from the Apple > devices. However, what I want is the non-blocking functionality which, > according to the

Re: kernel memory allocation failures

Chuck Silvers writes: > how about instead we fix the kmem_alloc() implementation to match the man > page? > that seems much more practical to me. adding failure checks and recovery code > to the thousands of *alloc() calls in the kernel would be a vast amount of > work > for

Re: kernel memory allocation failures

Chuck Silvers <c...@chuq.com> writes: > On Fri, Dec 11, 2015 at 09:44:07AM -0500, Greg Troxel wrote: >> >> Chuck Silvers <c...@chuq.com> writes: >> >> > how about instead we fix the kmem_alloc() implementation to match the man >> > page?

Re: Potential problem with reading data from usb devices with ugen(4)

Brian Buhrow writes: > If I'm using ehci(4) and option DIAGNOSTIC is defined, I get a panic: > "curlen == 0". That's a bug. DIAGNOSTIC should only be checking assertions about invariants that the code always maintains, not user input. So if there is a requirement

Re: Potential problem with reading data from usb devices with ugen(4)

Brian Buhrow writes: > To answer your question about whether there is a standard for > generating these packets, it seems there is not. Linux expects you to use > an ioctl() to generate the packet while FreeBSD expects you to send a write > request with 0 bytes, as we

  1   2   3   >