| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
MFC after: 3 days
|
| |
|
| |
|
|
|
|
| |
Many SIMs doesn't fill maxio field yet.
|
|
|
|
| |
It gives those beasts additional 10% of write bandwidth.
|
|
|
|
| |
(the improved version of) "load".
|
|
|
|
| |
initialization
|
|
|
|
|
|
|
| |
PR: kern/141289
Submitted by: Petr Lampa <lampa fit vutbr cz>
Approved by: rmacklem
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
"split" is very ineffective for devices with rotating media as HDDs.
To be effective, it needs that transfer time reduction due to block
splitting was bigger then access time increase due to non-sequential
access. For modern HDDs I was able to reproduce it only with read sizes
of 2MB and above, which is almost not applicable in real life.
"load" algorithm same time is more universal and effective now.
Reviewed by: pjd
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
only affects cases where open(2) is being used improperly - i.e. when the user
specifies O_APPEND without O_WRONLY or O_RDWR.
Reviewed by: rwatson
|
|
|
|
|
|
| |
ensure we don't overrun the end of the call chain.
MFC after: 1 week
|
|
|
|
| |
update this file to reflect the fact.
|
|
|
|
| |
into the checkin.
|
|
|
|
|
|
|
|
|
| |
hw.bge.forced_collapse. hw.bge.forced_collapse affects all bge(4)
controllers on system which may not desirable behavior of the
sysctl node. Also allow the sysctl node could be modified at any
time.
Reviewed by: bde (initial version)
|
| |
|
|
|
|
|
|
|
| |
Improve the algorithm the loader uses to choose a memory range for its
heap when using a range above 1MB.
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
Various small whitespace and style fixes.
|
|
|
|
|
|
|
|
|
|
|
| |
128 FIBs first and allocated more later if necessary. Remove now unused
definitions from the header file[1].
- Force sequential bus scanning. It seems parallel scanning is in fact
slower and causes more harm than good[1]. Adjust a comment to reflect that.
PR: kern/141269
Submitted by: Alexander Sack (asack at niksun dot com)[1]
Reviewed by: scottl
|
|
|
|
|
|
|
| |
disable mini ring withtout regard to mini ring support.
Reported by: marcel
Tested by: marcel
|
|
|
|
|
|
|
|
|
|
|
| |
drivers. These add new hardware support, most importantly
the pch (i5 chipset) in the em driver. Also, both drivers
now have the simplified (and I hope improved) watchdog
code. The igb driver uses the new RX cleanup that I
first implemented in ixgbe.
em - version 6.9.24
igb - version 1.8.4
|
|
|
|
| |
Submitted by: Paul B Mahol <onemda at gmail.com>
|
|
|
|
| |
Submitted by: Rohit Grover <rgrover1 at gmail.com>
|
|
|
|
|
|
|
| |
store. Writing to ar.bspstore is defined to leave ar.rnat undefined.
PR: ia64/120315
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds new feature support for the 82599, a hardware
assist to LRO, doing this required a large revamp to the
RX cleanup code because the descriptor ring may not be
processed out of order, this necessitated the elimination
of global pointers.
Additionally, the RX routine now does not refresh mbufs
on every descriptor, rather it will do a range, and then
update the hardware pointer at that time. These are
performance oriented changes.
The TX side now has a cleaner simpler watchdog algorithm
as well, in TX cleanup a read of ticks is stored, that
can then be compared in local_timer to determine if
there is a hang.
Various other cleanups along the way, thanks to all who
have provided input and testing.
|
|
|
|
|
| |
Pointed out by: jhb
Pointy hat: jkim
|
| |
|
|
|
|
|
| |
Obtained from: NetMos MCS9865 v1.0.0.1 driver
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
feature. These registers are reserved on controllers that have no
support for jumbo frame.
Only BCM5700 has mini ring so do not poke mini ring related
registers if controller is not BCM5700.
Reviewed by: marius
|
|
|
|
|
|
|
|
|
|
|
| |
handler in brgphy(4) does not exist and brgphy(4) just resets the
PHY and returns EINVAL as it has no isolation handler. I also agree
on Marius's opinion that stop handler of every NIC driver seems to
be the wrong place for implementing PHY isolate/power down.
If we need PHY isolate/power down it should be implemented in
brgphy(4) and users should administratively down the PHY.
Reviewed by: marius
|
|
|
|
|
|
| |
It makes MSI working there. Later (and cheaper) PCIe chips (3132/3531)
still randomly crashing system in few seconds of high MSI rates, generating
something inaporopriate, like NMI or "Fatal trap 30".
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
heap when using a range above 1MB.
Previously the loader would always use the last 3MB in the first memory
range above 1MB for the heap. However, this memory range is also where the
kernel and any modules are loaded. If this memory range is "small", then
using the high 3MB for the heap may not leave enough room for the kernel
and modules.
Now the loader will use any range below 4GB for the heap, and the logic to
choose the "high" heap region has moved into biosmem.c. It sets two
variables that the loader can use for a high heap if it desires. When a
high heap is enabled (BZIP2, FireWire, GPT, or ZFS), then the following
memory ranges are preferred for the heap in order from best to worst:
- The largest memory region in the SMAP with a start address greater than
1MB. The memory region must be at least 3MB in length. This leaves the
region starting at 1MB purely for use by the kernel and modules.
- The last 3MB of the memory region starting at 1MB if it is at least 3MB
in size. This matches the current behavior except that the current loader
would break horribly if the first region was not at least 3MB in size.
- The memory range from the end of the loader up to the 640k window. This
is the range the loader uses when none of the high-heap-requesting options
are enabled.
Tested by: hrs
MFC after: 1 week
|
|
|
|
|
|
| |
- Cleanup kernel messages, mostly PMP.
- Took references on devices, while PMP reinitializes them, to not let them
go and distort freeze reference counting.
|
|
|
|
| |
there without it as good as possible.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
1. Fixups are always done on 512 byte chunks (in stead of sectors). This
is kind of stupid.
2. Conevrt between NTFS blocknumbers (the blocksize equals the media
sector size) and the bread() and getblk() blocknr (which are 512-byte
sized)
NB: this change should not affect ntfs for 512-byte sector sizes.
|
|
|
|
|
|
|
|
|
|
| |
excluded, as it's used by MI code) and mode the sysctl variables from
pcpu_stats to pcpu_md.
Adjust all references accordingly.
While nearby, change the PCPU sysctl tree so that they match the CPU
device sysctl tree -- they are now children of a static node called
"machdep.cpu" and are named only with their cpu ID.
|
|
|
|
|
|
|
|
|
| |
Because several applications in /bin use libulog (or may use it in the
nearby future), it must not live inside /usr. It seems like we don't
need to add the copy from /usr/lib to ObsoleteFiles.inc, because it's
cleaned up during installation of libulog automatically.
Reported by: ume
|
|
|
|
|
|
|
| |
isc_atomic_xadd() and isc_atomic_cmpxchg().
Approved by: dougb@
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
allocating MAXCPU VHPTs up-front. This allows us to max-out MAXCPU
without memory waste -- MAXCPU is now 32 for SMP kernels.
This change also eliminates the VHPT scaling based in the total
memory in the system. It's the workload that determines the best size
of the VHPT. The workload can be affected by the amount of memory,
but not necessarily. For example, there's no performance difference
between VHPT sizes of 256KB, 512KB and 1MB when building the LINT
kernel. This was observed with a system that has 8GB of memory.
By default the kernel will allocate a 1MB VHPT. The user can tune the
system with the "machdep.vhpt.log2size" tunable.
|
|
|
|
| |
thorough security review has been completed.
|
|
|
|
|
| |
capability by snooping SDB FIS receive area. It should be even faster
then regular way, but less reliable.
|
|
|
|
|
|
|
| |
of setenv(), putenv() and unsetenv() when dealing with corrupt entries in
environ. They now output a warning and complete their task without error.
MFC after: 1 week
|
|
|
|
| |
prior to commit due to the problematic history of this code.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
instead of returning an error if a corrupt (not a "name=value" string) entry
in the environ array is detected when (re)-building the internal
environment. This should prevent applications or libraries from
experiencing issues arising from the expectation that these calls will
complete even with corrupt entries. The behavior is now as it was prior to
7.0.
Reviewed by: jilles
MFC after: 1 week
|