| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
| |
checks. Also indicate killpg(2) is POSIX compliant.
Reviewed by: jilles
Reviewed by: wblock
Approved by: cperciva
MFC after: 3 days
|
|
|
|
| |
Submitted by: alc
|
|
|
|
|
|
|
|
|
|
|
| |
output and replace it with a new visible sysctl kern.ipc.acceptqueue
of the same functionality. It specifies the maximum length of the
accept queue on a listen socket.
The old kern.ipc.somaxconn remains available for reading and writing
for compatibility reasons so that existing programs, scripts and
configurations continue to work. There no plans to ever remove the
orginal and now hidden kern.ipc.somaxconn.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Passing an invalid pointer results in undefined behaviour.
The wrappers in libthr access some of the data pointed to by the arguments
in userland, so that an invalid pointer will cause a signal and not an
[EFAULT] error return.
Furthermore, if the [EFAULT] error occurs when the kernel is writing, it is
not a proper error in the sense that the call still commits (changing the
signal disposition or accepting the signal).
MFC after: 1 week
|
| |
|
|
|
|
|
| |
control message and suggest to use LOCAL_CREDS setsockopt() for
reliability.
|
|
|
|
|
|
| |
three to four.
MFC after: 1 week
|
|
|
|
|
|
| |
PR: docs/170380
Submitted by: Garrett Cooper <yanegomi@gmail.com>
Approved by: joel (mentor)
|
|
|
|
|
|
|
|
| |
for process, thread or others we want to support.
Use the syscall to implement POSIX API clock_getcpuclock and
pthread_getcpuclockid.
PR: 168417
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Append '__' prefix to the tag of struct oflock, and put it under BSD
namespace. Structure is needed both by libc and kernel, thus cannot be
hidden under #ifdef _KERNEL.
Move a set of non-standard F_* and O_* constants into BSD namespace.
SUSv4 explicitely allows implemenation to pollute F_* and O_* names
after fcntl.h is included, but it costs us nothing to adhere
to the specification if exact POSIX compliance level is requested by
user code.
Change some spaces after #define to tabs.
Noted by and discussed with: bde
MFC after: 1 week
|
|
|
|
|
|
| |
F_DUPFD to make it less confusing, at least for me.
MFC after: 1 week
|
|
|
|
|
|
|
|
| |
put initially. They were added to head during development of 10-CURRENT, not
9-CURRENT.
Submitted by: glebius
Reviewed by: kib
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
clock_gettime(2) functions if supported. The speedup seen in
microbenchmarks is in range 4x-7x depending on the hardware.
Only amd64 and i386 architectures are supported. Libc uses rdtsc and
kernel data to calculate current time, if enabled by kernel.
Hopefully, this code is going to migrate into vdso in some future.
Discussed with: bde
Reviewed by: jhb
Tested by: flo
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
First, extend the changes in r230782 to better handle the common case
of using NOREUSE with sequential reads. A NOREUSE file descriptor
will now track the last implicit DONTNEED request it made as a result
of a NOREUSE read. If a subsequent NOREUSE read is adjacent to the
previous range, it will apply the DONTNEED request to the entire range
of both the previous read and the current read. The effect is that
each read of a file accessed sequentially will apply the DONTNEED
request to the entire range that has been read. This allows NOREUSE
to properly handle misaligned reads by flushing each buffer to cache
once it has been completely read.
Second, apply the same changes made to read(2) by r230782 and this
change to writes. This provides much better performance in the
sequential write case as it allows writes to still be clustered. It
also provides much better performance for misaligned writes. It does
mean that NOREUSE will be generally ineffective for non-sequential
writes as the current implementation relies on a future NOREUSE
write's implicit DONTNEED request to flush the dirty buffer from the
current write.
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
| |
The stat structures returned on pipes seems to contain all the
information required by POSIX. Especially the wording "and thus to a
pipe" makes little sense, because it seems to imply a certain
relationship between sockets and pipes that simply isn't there.
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 3 days
|
|
|
|
| |
of our manual pages.
|
|
|
|
|
| |
PR: 167713
Submitted by: Nobuyuki Koganemaru (kogane!jp.freebsd.org)
|
|
|
|
|
| |
Submitted by: Norman Hardy
MFC after: 3 days
|
|
|
|
|
| |
Submitted by: Norman Hardy
MFC after: 3 days
|
|
|
|
|
|
|
| |
PR: docs/167201
Submitted by: Kurt Jaeger <fbsd-ports@opsec.eu>
Approved by: cperciva
MFC after: 3 days
|
|\
| |
| |
| |
| |
| | |
currently done by /etc/rc.d/jail.
MFC after: 3 months
|
| | |
|
| |
| |
| |
| | |
- Follow the same macros used in device driver manual pages.
|
| |
| |
| |
| | |
Submitted by: bde
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
outside the range of valid file descriptors
PR: kern/164970
Submitted by: Peter Jeremy <peterjeremy@acm.org>
Reviewed by: jilles
Approved by: cperciva
MFC after: 1 week
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
privilege attempts to toggle SF_SETTABLE flags.
- Use the '^' operator in the SF_SNAPSHOT anti-toggling check.
Flags are now stored to ip->i_flags in one place after all checks.
Submitted by: bde
|
| | |
|
| |
| |
| |
| |
| | |
this syntax violation and while I'm here also convert <TAB> to Ta and adjust
quotation marks in order to prevent this problem in the future.
|
| |
| |
| |
| |
| |
| |
| | |
Disussed with: gavin
No objection from: doc
Approved by: joel
MFC after: 3 days
|
| |
| |
| |
| |
| | |
Reviewed by: gjb
Approved by: sbruno
|
| | |
|
| | |
|
| |
| |
| |
| | |
Approved by: hrs (mentor)
|
| |
| |
| |
| |
| |
| |
| |
| | |
how it may be set, and current limitations on the value.
Approved by: hrs (mentor)
PR: docs/157453
MFC after: 1 week
|
| |
| |
| |
| |
| |
| |
| |
| | |
Document EIO from msync(2).
Inspired by PR: docs/165929 [1]
Reviewed by: jilles
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| |
| |
| | |
This errno can also be returned if the passed process identifier doesn't
correspond with a process group.
Discussed on: arch@
MFC after: 1 week
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
On FreeBSD, all processes have a process group, so it is impossible for
kill(2) to fail this way. POSIX also doesn't mention this error
condition.
Discussed on: arch@
MFC after: 3 weeks
|
| | |
|
| |
| |
| |
| | |
MFC after: 3 days
|
| |
| |
| |
| |
| |
| | |
Discussed with: bz
Reviewed by: glebius
MFC after: 2 weeks
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
o Wrap sentences on to new lines
o Cleanup trailing whitespace
Found with: textproc/igor
MFC after: 1 week
X-MFC-With: r232157
|
| |
| |
| |
| |
| |
| | |
Submitted by: amdmi3
PR: 165431
MFC after: 1 week
|
| |
| |
| |
| | |
MFC after: 3 days
|
| | |
|
| |
| |
| |
| |
| |
| | |
which enables thread-friendly polling on same fd for AIO events.
Reviewed by: delphij
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The reasoning behind this, is that if we are consistent in our
documentation about the uint*_t stuff, people will be less tempted to
write new code that uses the non-standard types.
I am not going to bump the man page dates, as these changes can be
considered style nits. The meaning of the man pages is unaffected.
MFC after: 1 month
|
| |
| |
| |
| | |
MFC after: 1 week
|