kttcp(4) [netbsd man page]

KTTCP(4)						   BSD Kernel Interfaces Manual 						  KTTCP(4)

NAME

     kttcp -- kernel support for testing network throughput

SYNOPSIS

     pseudo-device kttcp

DESCRIPTION

     This driver provides kernel support for testing network throughput from the perspective of the kernel.  It is similar in spirit to the clas-
     sic ttcp network benchmark program, the main difference being that with kttcp, the kernel is the source and sink of the data.

     Testing like this is useful for a few reasons:

     1.   This allows us to know what kind of performance we can expect from network applications that run in the kernel space, such as the NFS
	  server or the NFS client.  These applications don't have to move the data to/from userspace, and so benchmark programs which run in
	  userspace don't give us an accurate model.

     2.   Since data received is just thrown away, the receiver is very fast.  This can provide better exercise for the sender at the other end.

     3.   Since the NetBSD kernel currently uses a run-to-completion scheduling model, kttcp provides a benchmark model where preemption of the
	  benchmark program is not an issue.

SEE ALSO

     pkgsrc/benchmarks/kttcp, pkgsrc/benchmarks/ttcp

BSD
								 December 2, 2006							       BSD

RUMP_NFS(8)						    BSD System Manager's Manual 					       RUMP_NFS(8)

NAME

     rump_nfs -- mount a nfs share with a userspace server

SYNOPSIS

     file-system PUFFS
     pseudo-device putter

     rump_nfs [options] share mountpoint

DESCRIPTION

     NOTE! This manual page describes features specific to the rump(3) file server.  Please see mount_nfs(8) for a full description of the avail-
     able command line options.

     The rump_nfs utility can be used to mount nfs file systems.  It uses rump(3) and p2k(3) to facilitate running the file system as a server in
     userspace.  As opposed to mount_nfs(8), rump_nfs does not use file system code within the kernel and therefore does not require kernel sup-
     port except puffs(4).  Apart from a minor speed penalty there is no downside with respect to in-kernel code.

     Even though the rump_nfs file system client runs within a virtual rump kernel in userspace, it uses host network services (by means of ``rump
     sockin'').  This means that regardless of whether using rump_nfs or mount_nfs(8), the same network configurations will be used.  Currently,
     ``sockin'' supports IPv4.

     To use rump_nfs via mount(8), the flags -o rump and -t nfs should be given.  Similarly, rump_nfs is used instead of mount_nfs(8) if ``rump''
     is added to the options field of fstab(5).

SEE ALSO

     p2k(3), puffs(3), rump(3), mount_nfs(8)

HISTORY

     The rump_nfs utility first appeared in NetBSD 5.0.

BSD
								 November 21, 2010							       BSD