Revision tags: v4.0.4 |
|
#
5e5bfdd9 |
| 03-Feb-2015 |
Sascha Wildner <saw@online.de> |
kernel/ath: Disallow overriding ATH_RXBUF and ATH_TXBUF.
They are now forced to 512.
|
#
0fb2ae13 |
| 28-Jan-2015 |
Sascha Wildner <saw@online.de> |
kernel: Retire the P1003_1B and _KPOSIX_VERSION kernel options.
|
Revision tags: v4.0.3 |
|
#
2a1ad637 |
| 08-Jan-2015 |
François Tigeot <ftigeot@wolfpond.org> |
sound: Import latest code from FreeBSD
* As of 1bac48ea8f21c4121f1c45311ec4f05577c58abc (SVN id r275101) "Add bunch of PCI IDs of Intel Wildcat Point (9 Series) chipsets."
* Do not import isa, ma
sound: Import latest code from FreeBSD
* As of 1bac48ea8f21c4121f1c45311ec4f05577c58abc (SVN id r275101) "Add bunch of PCI IDs of Intel Wildcat Point (9 Series) chipsets."
* Do not import isa, macio, sbus and usb drivers
* snd_au88x0 has been removed. According to the FreeBSD commit message, it never even got compiled into the kernel or as a module.
* Drop the ds1, csa and maestro3 drivers due to restrictive license terms or the need to use binary blobs. These drivers are not built by default on FreeBSD.
show more ...
|
#
60a260ad |
| 07-Jan-2015 |
Sascha Wildner <saw@online.de> |
kernel: Remove our ancient SCTP support.
It was based on an early stage of FreeBSD's support and never got beyond that point, due to lack of usage and lack of maintenance.
It is also kind of standi
kernel: Remove our ancient SCTP support.
It was based on an early stage of FreeBSD's support and never got beyond that point, due to lack of usage and lack of maintenance.
It is also kind of standing the the way of ongoing work in the IPv6 stack by sephe.
If anyone ever wants to start again on upgrading and maintaining it, they can decide then if reverting this commit again makes sense as a base.
Requested-by: sephe Approved-by: dillon
show more ...
|
Revision tags: v4.0.2 |
|
#
b981a49d |
| 25-Dec-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
socket: Add KTR_SOWAKEUP
Define 2 pairs of children nodes for this KTR, which are used to tracking extra IPIs for accept(2).
Note: The tracked sorwakeup() and the wakeup(so_timeo) does not generate
socket: Add KTR_SOWAKEUP
Define 2 pairs of children nodes for this KTR, which are used to tracking extra IPIs for accept(2).
Note: The tracked sorwakeup() and the wakeup(so_timeo) does not generate extra (wakeup) IPIs.
show more ...
|
#
05eff656 |
| 29-Nov-2014 |
Sascha Wildner <saw@online.de> |
kernel: Remove the no longer used KTR_USB_MEMORY option.
|
Revision tags: v4.0.1 |
|
#
6bedbebc |
| 16-Nov-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
build: Add ICMPPRINTFS as global option
|
Revision tags: v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2 |
|
#
39b3e0a1 |
| 29-Jul-2014 |
Sascha Wildner <saw@online.de> |
kernel: Completely remove the obsolete DEVICE_POLLING and SMP options.
DEVICE_POLLING is IFPOLL_ENABLE and SMP is the default for some time now.
|
#
10ceb702 |
| 29-Jul-2014 |
Sascha Wildner <saw@online.de> |
kernel: Make sysvipc syscalls non-optional.
Before this commit, we had three related kernel options, SYSVMSG, SYSVSEM and SYSVSHM, to enable the syscalls. They were in all our configs, but in theory
kernel: Make sysvipc syscalls non-optional.
Before this commit, we had three related kernel options, SYSVMSG, SYSVSEM and SYSVSHM, to enable the syscalls. They were in all our configs, but in theory the user could disable the functionality. Having to deal with scenarios where they are not available is unnecessarily complicated and there seems to be no real reason to want to disable them.
For convenience, leave the three options as no-ops for now, so adjusting the kernel config is not necessarily needed. We'll change them to being unknown at some later point.
This commit also removes some parts which assumed that we had sysvmsg.ko, sysvsem.ko and sysvshm.ko modules, like FreeBSD, but this assumption was never true on DragonFly.
show more ...
|
Revision tags: v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc |
|
#
6d688f9b |
| 21-May-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
udp: Add KTR to measure UDP packet creation and ip_output cost
|
#
6836e2b4 |
| 11-May-2014 |
Sascha Wildner <saw@online.de> |
kernel/acpi: Add some ktr events to the acpi_ec code.
Translates what FreeBSD has to our ktr(9) syntax.
Also, reduce differences with FreeBSD in some other places but it is just cosmetical.
|
#
7c87aae6 |
| 01-May-2014 |
Sascha Wildner <saw@online.de> |
Remove ATM protocol support.
FreeBSD ditched it about 6 years ago. Also, I'm not sure if this ever worked on x86_64.
|
#
11c3c8f7 |
| 21-Apr-2014 |
Sascha Wildner <saw@online.de> |
kernel: Remove some unused options (forgotten in the IPX removal).
|
#
6f25d555 |
| 20-Apr-2014 |
Sascha Wildner <saw@online.de> |
Remove support for the IPX and NCP protocols, and for NWFS.
This was on the list for a longer time now. FreeBSD removed it recently, too. Their commit msg has some more info:
"IPX was a network tra
Remove support for the IPX and NCP protocols, and for NWFS.
This was on the list for a longer time now. FreeBSD removed it recently, too. Their commit msg has some more info:
"IPX was a network transport protocol in Novell's NetWare network operating system from late 80s and then 90s. The NetWare itself switched to TCP/IP as default transport in 1998. Later, in this century the Novell Open Enterprise Server became successor of Novell NetWare. The last release that claimed to still support IPX was OES 2 in 2007. Routing equipment vendors (e.g. Cisco) discontinued support for IPX in 2011."
The commit removes support for NCP (NetWare Core Protocol) and NWFS (NetWare File System) along with it (both gone from FreeBSD too since a while).
show more ...
|
Revision tags: v3.6.2 |
|
#
a0ab8429 |
| 27-Mar-2014 |
Imre Vadasz <imre@vdsz.com> |
bwn: Porting from FreeBSD
* Adding bwn and siba_bwn to sys/conf/files and to the X86_64_GENERIC kernel configuration.
* Replacing BWN_LOCK, BWN_UNLOCK, BWN_ASSERT_SERIALIZED with wlan_global_se
bwn: Porting from FreeBSD
* Adding bwn and siba_bwn to sys/conf/files and to the X86_64_GENERIC kernel configuration.
* Replacing BWN_LOCK, BWN_UNLOCK, BWN_ASSERT_SERIALIZED with wlan_global_serializer.
* Increasing some alignments from 4K to 8K and some from 1 byte to 4 bytes.
* Changing slot counts for RX and TX from 64 to 256, which is the same size as used by b43 in Linux.
* Allow overriding the BWN_TXRING_SLOTS and BWN_RXRING_SLOTS values in the kernel configuration.
* Some style fixes. Removing unneeded NULL checks.
* Replace a DELAY(50000) with tsleep.
* Can't use kmalloc to allocate memory for dma like in FreeBSD and Linux.
* A few typo and grammar fixes in the bwn.4 manpage.
show more ...
|
Revision tags: v3.6.1 |
|
#
50a82a17 |
| 03-Jan-2014 |
Sascha Wildner <saw@online.de> |
kernel/ath: Make it compile into the kernel again and re-add to GENERIC.
Full list of changes:
* Adjust the 'files' file for changed ath_hal path and additional source.
* Add options from FreeBS
kernel/ath: Make it compile into the kernel again and re-add to GENERIC.
Full list of changes:
* Adjust the 'files' file for changed ath_hal path and additional source.
* Add options from FreeBSD and comment those out which are not compiling/used. Add the remaining ones to the LINT kernels for additional build checking.
* Fix some typos in the ar9300 code.
* Use ath_hal_ether_sprintf() where needed.
* Add some casts to work around -Wenum-compare and -Wformat breakage.
* Comment out some unused struct ifp's and FreeBSD's ktr.
* Slightly readjust ATH_RXBUF and ATH_TXBUF handling to let the kernel options of the same name override the defaults. In the GENERIC kernel and module everything stays the same.
* Use the (slightly better structured) FreeBSD Makefile for ath_hal.
All kernels compile with ath(4) as of this commit.
show more ...
|
#
79251f5e |
| 24-Nov-2013 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
ix: Import Intel ixgbe-2.5.15
MSI and legacy interrupt (line based interrupt) are working as of this commit. polling(4) will be supported and MSI-X will be brought back in the later commits.
ixgbe
ix: Import Intel ixgbe-2.5.15
MSI and legacy interrupt (line based interrupt) are working as of this commit. polling(4) will be supported and MSI-X will be brought back in the later commits.
ixgbe is renamed to ix, which is consistent w/ the interface name, and this makes 'ifconfig ix0' work as expected.
Local changes: - Reorganize RX and TX ring data structure; nuke useless 'queue'. - Rework RX and TX ring creation, destroy, initialization and cleanup. - Reorganize interrupt related data structure. This also prepares for bringing MSI-X back. - Rework interrupt allocation. - Rework MSI and legacy interrupt handler. - Enable RSS (2 RX rings) even if MSI or legacy interrupt is used. - Apply DragonFly specific RSS configuration. - Partially rework RX code path. - Enable TX header write-back. - Rework TX code path and TX watchdog mechanism. - Rework busdma(9) related bits. - Rework ifnet.if_ioctl method. - Reorganize initialize and stop code. - Reorganize attach and detach code. - Code clean up.
show more ...
|
#
459cf836 |
| 25-Nov-2013 |
Sascha Wildner <saw@online.de> |
kernel/iwn: Put some finishing touches to the recent upgrade.
* Adjust 'files' to unbreak LINT.
* Add IWN_DEBUG option.
* Update manual pages.
* Update SVN IDs.
Taken-from: FreeBSD
|
Revision tags: v3.6.0, v3.7.1, v3.6.0rc, v3.7.0 |
|
#
95ff9ed0 |
| 29-Oct-2013 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
polling: Add preliminary KTR support
|
Revision tags: v3.4.3 |
|
#
181bd34e |
| 10-Aug-2013 |
Sascha Wildner <saw@online.de> |
kernel: Start removing syslink.
It's tied in with a few things that we don't want to break, so care is needed.
Approved-by: dillon
|
Revision tags: v3.4.2, v3.4.0, v3.4.1 |
|
#
695a8586 |
| 17-Apr-2013 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
bnx: Implement multiple RX/TX rings and MSI-X support for 5718/57785
BCM5718 and BCM57785 families support 4 RX rings and 5 MSI-X vectors. Additionally BCM5719/BCM5720 support 4 TX rings, while othe
bnx: Implement multiple RX/TX rings and MSI-X support for 5718/57785
BCM5718 and BCM57785 families support 4 RX rings and 5 MSI-X vectors. Additionally BCM5719/BCM5720 support 4 TX rings, while other chips in these two families only support 1 TX ring. Each MSI-X vector has its own interrupt moderation parameters.
Hardware supplied RSS hash and packet type are not utilized yet; they will be supported in the upcoming commits.
This commit also fixes some RX standard ring refilling races introduced in: 841cdf08263117c54b0a800440c7630b6913c21e
RX standard ring refilling scheduling may enjoy futher optimization.
show more ...
|
Revision tags: v3.4.0rc, v3.5.0 |
|
#
d88b9605 |
| 29-Mar-2013 |
Sascha Wildner <saw@online.de> |
kernel: Remove 'options COMPAT_SUNOS'.
It was supposed to provide binary compatibility with SunOS 4.x for the sparc32 port of 4.4BSD.
|
#
b42386ee |
| 27-Feb-2013 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
bce: Implement multiple TX/RX rings and MSI-X support for 5709/5716
5709/5716 support 9 RX rings, 9 TX rings and 9 MSI-X vectors; each MSI-X vector has its own interrupt moderation parameters.
(N +
bce: Implement multiple TX/RX rings and MSI-X support for 5709/5716
5709/5716 support 9 RX rings, 9 TX rings and 9 MSI-X vectors; each MSI-X vector has its own interrupt moderation parameters.
(N + 1) RX rings, N TX rings and (N + 1) MSI-X vectors will be enabled; N is ncpus2, if ncpus2 is less than 8, else N will be 8.
The extra RX ring is enabled mainly because: The first RX ring is only used for packets whose RSS hash could not be calculated, so it is actually _not_ involved in RSS. This extra RX ring is used for the packets whose masked RSS hash equal 0.
An extra MSI-X vector is allocated for this extra RX ring; there is no correponding TX ring for this extra RX ring. In polling(4), this extra RX ring is polled along with the first RX ring in the first RX polling handler, in which the packets whose RSS hash equal 0 should be processed.
Hardware provided RSS hash and packet type are not utilized yet; they will be supported in the upcoming commits.
Related hardware registers and hardware initialization order are infered from Linux's bnx2 (*); NetXtremeII-PG203-R.pdf provided on Broadcom's website does not contain enough information for multiple rings and MSI-X to function.
(*) Unlike Linux's bnx2, which limits number of RX rings to 8, DragonFly limits number of RX rings to 9 and 9 RX rings actually work quite well.
show more ...
|
#
d84018e9 |
| 07-Feb-2013 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
emx: Implement multiple hardware TX queue support; disabled by default
Two notes about the multiple hardware TX queue support:
- It could only be enabled on 82571, 82572 and es2lan. Enabling it on
emx: Implement multiple hardware TX queue support; disabled by default
Two notes about the multiple hardware TX queue support:
- It could only be enabled on 82571, 82572 and es2lan. Enabling it on 82574, whose datasheet claims multiple hardware TX queue support, could cause watchdog timeout when heavy TCP receiving test are conducted.
- It is disabled by default. Since 82571, 82572 and es2lan only have one global context for TX hardware checksum and TSO, the driver will have to setup TX context descriptor for each packet. Using TX context descriptor for each packet could cause serious transmission performance regression for tiny packets, see comment of following commit: 51e6819fc2ad7cefdf830dcc9f20bcbe2af2aa52
However, multiple hardware TX queues still could be enabled depending on the workload (*): o TSO probably are not affected by setting up a TX context descriptor for each TSO packet. o Stuffs do not using hardware TX checksum, e.g. IP fast forwarding.
Multiple hardware TX queues could be enabled globally by tunable: hw.emx.txr=2 Multiple hardware TX queues could be enabled on individual interface by tunable: hw.emxY.txr=2
(*) Another thought is to add per-interface metric, which indicates the size of packets that worth hardware checksum; if the packets' size is below that metric, software checksum is used.
show more ...
|
#
4e19e38a |
| 28-Jan-2013 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
igb: Add IGB_TSS_DEBUG kernel option
|