| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
only happen on every Nth call. Update the existing twiddle() calls done in
various IO loops to roughly reflect the relative IO sizes. That is, tftp
and nfs call twiddle() on every 1K block, ufs on every filesystem block,
so the network calls now use a much larger divisor than disk IO calls.
Also add a new twiddle_divisor() function that allows an application to set
a global divisor that is applied on top of the per-call divisors. Nothing
calls this yet, but loader(8) will be using it to further throttle the
cursor for slow serial consoles.
|
|
|
|
|
|
|
|
| |
There is an oppinion that result of that equation is compiler-specific.
Submitted by: dt71@gmx.com, kientzle
Reviewed by: rmacklem
MFC after: 3 days
|
|
|
|
|
|
| |
free(3) handles NULL parameter fine.
Reviewed by: kib, Garrett Cooper
|
| |
|
|
|
|
|
|
| |
buffer. For now it fixes bug when following `ls` command will return data
from previous one aborted by pager. Also it should allow to read several
directories same time, for example, for recursive tracerse.
|
|
|
|
| |
fields that should be file-specific.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows the nfs_getrootfh() function to return the
correct file handle size to pxe.c for pxeboot. It also
results in NFSv2 no longer being used by default anywhere
in FreeBSD. If built with OLD_NFSV2 defined, the old
code that predated this patch will be built and NFSv2
will be used.
Tested by: danny at cs.huji.ac.il
MFC after: 2 weeks
|
|
|
|
| |
files with NetBSD / OpenBSD versions.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- bzipfs and gzipfs now properly return errno values directly from their
read routines rather than returning -1.
- missing errno values on error returns for the seek routines on almost
all filesystems were added.
- fstat() now returns -1 if an error occurs rather than ignoring it.
- nfs's readdir() routine now reports valid errno values if an error or
EOF occurs rather than EPERM (It was just returning 0 for success and
1 for failure).
- nullfs used the wrong semantics for every function besides close() and
seek(). Getting it right for close() appears to be an accident at that.
- read() for buffered files no longer returns 0 (EOF) if an error occurs,
but returns -1 instead.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
file in the NFS file system when the underlying device is not a
network device. A Sparc64 specific hack for this exact problem was
already present (nfs.c:1.9, tftp.c:1.10), but the problem is not
specific to Sparc64. The hack has been promoted to a non-i386 test
because on non-i386 architectures it's either impossible to have
non-network devices coexist in the same loader with the NFS FS, or
network and non-network device coexist and NFS filesystems can only
be used on top of network devices. I believe i386 pxeboot is where
this does not hold.
The root cause of this problem is in open.c where each file system
is tried until no more file systems exist or a file system returns
success. There's no notion of a list of valid file systems given
the underlying device and the non-existence of a file can cause
the invalid combination to be tried.
|
|
|
|
| |
to pick up, ala pxe.
|
|
|
|
| |
devices as though they were backed by network devices.
|
| |
|
| |
|
|
|
|
| |
NFS filehandle for the root mount.
|
| |
|
|
|
|
|
| |
node is statically allocated and is not guarded, so free will panic
in nfs_close.
|
|
|
|
| |
functionality for some of the filesystesms.
|
|
|
|
|
|
| |
them.
Submitted by: write-protected text segment in BTX
|
|
modules).
Obtained from: NetBSD, with some architectural changes and many additions.
|