{"commits":[{"author":{"name":"bz","email":"0c17ddceb3071d32d637bf884d4ad3d465c295fe@FreeBSD.org"},"sha":"9f361b4d6ab5f01d72d5a63caf16298d51e87496","message":"The maximum TSO frame size should be:\n\tmaximum IP datagram size (65535 bytes) +\n\tEthernet header size (14 bytes) +\n\t2 * VLAN tag size (4 bytes) [1].\n\n[1] We need to multiply by 2 to account for the double VLAN tag\n    provision added in IEEE 802.1ad.\n\nSubmitted by:\tDavid Somayajulu (david.somayajulu qlogic.com)\nMFC after:\t4 days","url":"https://api.github.com/repos/freebsd/freebsd/commits/9f361b4d6ab5f01d72d5a63caf16298d51e87496"},{"author":{"name":"mjacob","email":"4aae94ac6bf5bb518d7c49acf09db49c7a0922d2@FreeBSD.org"},"sha":"e48086827e5b62b39dbbed403c805a882bf2cb62","message":"Was chasing down a failure to load f/w on a 2400. It turns out that the card\nis actually broken, or needs a BIOS upgrade for 64 bit loads, but this uncovered\na couple of misplaced opcode definitions and some missing continual mbox command\ncases, so might as well update them here.","url":"https://api.github.com/repos/freebsd/freebsd/commits/e48086827e5b62b39dbbed403c805a882bf2cb62"},{"author":{"name":"pho","email":"95d52f002fbe52e113b946f0a44e1b41ec05153b@FreeBSD.org"},"sha":"bc0e45d2e467a8b2ad8d12d548e5d03d589b17f5","message":"Handle invalid large values for getdirentries(2) data buffer size.\n\nIn collaboration with:\tkib\nReviewed by:\tdes\nReported by:\tThe iknowthis syscall fuzzer.\nMFC after:\t1 week","url":"https://api.github.com/repos/freebsd/freebsd/commits/bc0e45d2e467a8b2ad8d12d548e5d03d589b17f5"},{"author":{"name":"jhb","email":"bfed11ad5cdd21dfd9ed695a5c3e9ad4e680f6af@FreeBSD.org"},"sha":"6a6b435eaa59743d10bae8e46f90c27965e2d3fb","message":"Add single-message MSI support to mfi(4).  It is disabled by default but\ncan be enabled via the hw.mfi.msi tunable.  Many mfi(4) controllers also\nsupport MSI-X, but in testing it seems that many adapters do not work with\nMSI-X but do work with MSI.\n\nMFC after:\t2 weeks","url":"https://api.github.com/repos/freebsd/freebsd/commits/6a6b435eaa59743d10bae8e46f90c27965e2d3fb"},{"author":{"name":"alc","email":"403c7ec3b0314e7b36282e6cab7b45ab65013fab@FreeBSD.org"},"sha":"c95ea9582b0fdd3e2c3688834f5e460d5f1919fc","message":"Refactor the code that performs physically contiguous memory allocation,\nyielding a new public interface, vm_page_alloc_contig().  This new function\naddresses some of the limitations of the current interfaces, contigmalloc()\nand kmem_alloc_contig().  For example, the physically contiguous memory that\nis allocated with those interfaces can only be allocated to the kernel vm\nobject and must be mapped into the kernel virtual address space.  It also\nprovides functionality that vm_phys_alloc_contig() doesn't, such as wiring\nthe returned pages.  Moreover, unlike that function, it respects the low\nwater marks on the paging queues and wakes up the page daemon when\nnecessary.  That said, at present, this new function can't be applied to all\ntypes of vm objects.  However, that restriction will be eliminated in the\ncoming weeks.\n\nFrom a design standpoint, this change also addresses an inconsistency\nbetween vm_phys_alloc_contig() and the other vm_phys_alloc*() functions.\nSpecifically, vm_phys_alloc_contig() manipulated vm_page fields that other\nfunctions in vm/vm_phys.c didn't.  Moreover, vm_phys_alloc_contig() knew\nabout vnodes and reservations.  Now, vm_page_alloc_contig() is responsible\nfor these things.\n\nReviewed by:\tkib\nDiscussed with:\tjhb","url":"https://api.github.com/repos/freebsd/freebsd/commits/c95ea9582b0fdd3e2c3688834f5e460d5f1919fc"},{"author":{"name":"philip","email":"3ba3974e96044dcde818e6310ed799abe10671d4@FreeBSD.org"},"sha":"179a36537f5355ccc68afb883153a249348a8bc8","message":"Add the sfxge(4) device driver, providing support for 10Gb Ethernet adapters\nbased on Solarflare SFC9000 family controllers.  The driver supports jumbo\nframes, transmit/receive checksum offload, TCP Segmentation Offload (TSO),\nLarge Receive Offload (LRO), VLAN checksum offload, VLAN TSO, and Receive Side\nScaling (RSS) using MSI-X interrupts.\n\nThis work was sponsored by Solarflare Communications, Inc.\n\nMy sincere thanks to Ben Hutchings for doing a lot of the hard work!\n\nSponsored by:\tSolarflare Communications, Inc.\nMFC after:\t3 weeks","url":"https://api.github.com/repos/freebsd/freebsd/commits/179a36537f5355ccc68afb883153a249348a8bc8"},{"author":{"name":"kib","email":"67150a9dcf8948cde92f2ba91d8ada0d3335c521@FreeBSD.org"},"sha":"006e60f568b8a0fd35a4856294ea6de46fb08422","message":"Fix build, use %d for int value formatting.","url":"https://api.github.com/repos/freebsd/freebsd/commits/006e60f568b8a0fd35a4856294ea6de46fb08422"},{"author":{"name":"kib","email":"67150a9dcf8948cde92f2ba91d8ada0d3335c521@FreeBSD.org"},"sha":"96d473f87b814762d54c14d1161e8075ddf9972c","message":"The sys/sysctl.h header is needed when MFI_DEBUG is defined.\n\nNod from:\tjhb","url":"https://api.github.com/repos/freebsd/freebsd/commits/96d473f87b814762d54c14d1161e8075ddf9972c"},{"author":{"name":"pjd","email":"4f107de606760b375e4f4cdea54fd8040bd474ad@FreeBSD.org"},"sha":"90fc9caac51eda86b2a0348a3484597e1773beca","message":"Fix make universe.","url":"https://api.github.com/repos/freebsd/freebsd/commits/90fc9caac51eda86b2a0348a3484597e1773beca"},{"author":{"name":"pjd","email":"4f107de606760b375e4f4cdea54fd8040bd474ad@FreeBSD.org"},"sha":"eb4dbc3ef45878456cd3b1b71d2e9fb627db0fc1","message":"Constify stack argument for functions that don't modify it.\n\nReviewed by:\ted, kib, jhb","url":"https://api.github.com/repos/freebsd/freebsd/commits/eb4dbc3ef45878456cd3b1b71d2e9fb627db0fc1"},{"author":{"name":"yongari","email":"79c7d24101a3af56696b485dbd1362edab3b7da5@FreeBSD.org"},"sha":"828728308214b12fc24e4ad96f2d82f40a918317","message":"Enable 64bit DMA addressing support for all msk(4) controllers.\nUnnecessarily complex LE format used on Marvell controller was\nmain reason not to enable 64bit DMA addressing in driver.  If high\n32bit address of DMA address of TX/RX buffer is changed, driver has\nto generate a new LE.  In TX path, driver will keep track of lastly\nused high 32bit address of DMA address and generate a new LE\nwhenever it sees high address change in the DMA address. In RX path,\ndriver will always use two LEs to specify 64bit DMA address of RX\nbuffer.  If the high 32bit address of DMA address of RX buffer is\nthe same as previous DMA address of RX buffer, driver does not have\nto use two LEs but driver will use two LEs for simplicity in RX\nring management.\n\nOne of draw back for switching to 64bit DMA addressing is that the\nlarge amount of LEs are used to specify 64bit DMA address such that\nnumber of available LEs for TX/RX buffers are considerably reduced.\nTo mitigate the issue, increase number of available LEs from 256 to\n384 for TX and from 256 to 512 for RX. For 32bit architectures,\nmsk(4) does not use 64bit DMA addressing to save resources.\n\nTested by:\tdas","url":"https://api.github.com/repos/freebsd/freebsd/commits/828728308214b12fc24e4ad96f2d82f40a918317"},{"author":{"name":"andreast","email":"4cbed289be6f7eb01013ae0dcf9702df42c1a6aa@FreeBSD.org"},"sha":"23357404f2cebe3e9e1ab2d3527eff78891b3d75","message":"Copy over the ASM_DECLARE_FUNCTION_SIZE macro from linux64.h. This macro\ndeclares the proper size of a function. Without this macro recent GNU as will\ncomplain about with:\n'Error: .size expression for main does not evaluate to a constant.'\n\nUp to now we produce this:\n\n.L.main:\n \t....\n\t.size   main, .-main\n\nWith the macro defined the output is this:\n\n.L.main:\n \t....\n\t.size   main,.-.L.main\n\nThis affects only the 64-bit compiler.\nTested with world and kernel on both, 32 and 64-bit powerpc.","url":"https://api.github.com/repos/freebsd/freebsd/commits/23357404f2cebe3e9e1ab2d3527eff78891b3d75"},{"author":{"name":"yongari","email":"79c7d24101a3af56696b485dbd1362edab3b7da5@FreeBSD.org"},"sha":"64141934a1299df6c7d1a849b030a5caf9eb0fa8","message":"Add preliminary support for RTL8402 PCIe FastEthernet with\nintegrated card reader.\n\nH/W donated by:\tRealTek Semiconductor Corp.","url":"https://api.github.com/repos/freebsd/freebsd/commits/64141934a1299df6c7d1a849b030a5caf9eb0fa8"},{"author":{"name":"pjd","email":"4f107de606760b375e4f4cdea54fd8040bd474ad@FreeBSD.org"},"sha":"4cfa095f1ed6f72c65554046fc95d3239f8ca2c1","message":"Constify arguments for locking KPIs where possible.\n\nThis enables locking consumers to pass their own structures around as const and\nbe able to assert locks embedded into those structures.\n\nReviewed by:\ted, kib, jhb","url":"https://api.github.com/repos/freebsd/freebsd/commits/4cfa095f1ed6f72c65554046fc95d3239f8ca2c1"},{"author":{"name":"imp","email":"7ebbccbf2a9ebaa9338648798afddf195f6f1b63@FreeBSD.org"},"sha":"1b32c5bff86dd1a6119e708b72ded45f5e585cc6","message":"Add helpful clarification text.  While not strictly necessary, these\nfew words make this man page much easier to understand without\nre-reading prior parts of the man page.","url":"https://api.github.com/repos/freebsd/freebsd/commits/1b32c5bff86dd1a6119e708b72ded45f5e585cc6"},{"author":{"name":"yongari","email":"79c7d24101a3af56696b485dbd1362edab3b7da5@FreeBSD.org"},"sha":"28f401ff5bfc42c12589548a583a42bd6a9773f4","message":"Add preliminary support for RTL8411 PCIe Gigabit ethernet with\nintegrated card reader.\n\nH/W donated by:\tRealTek Semiconductor Corp.","url":"https://api.github.com/repos/freebsd/freebsd/commits/28f401ff5bfc42c12589548a583a42bd6a9773f4"},{"author":{"name":"yongari","email":"79c7d24101a3af56696b485dbd1362edab3b7da5@FreeBSD.org"},"sha":"8555be6871c2d4b10904ca5c7eb2d2ae51d9cbbe","message":"Add missing driver lock in SIOCSIFCAP handler.","url":"https://api.github.com/repos/freebsd/freebsd/commits/8555be6871c2d4b10904ca5c7eb2d2ae51d9cbbe"},{"author":{"name":"yongari","email":"79c7d24101a3af56696b485dbd1362edab3b7da5@FreeBSD.org"},"sha":"c14de6af917c0db8017fa4dea528fe1c84d917ec","message":"Disable PCIe ASPM (Active State Power Management) for all\ncontrollers.\nMore and more RealTek controllers started to implement EEE feature.\nVendor driver seems to load a kind of firmware for EEE with\nadditional PHY fixups.  It is known that the EEE feature may need\nASPM support.  Unfortunately there is no documentation for EEE of\nthe controller so enabling ASPM may cause more problems.","url":"https://api.github.com/repos/freebsd/freebsd/commits/c14de6af917c0db8017fa4dea528fe1c84d917ec"},{"author":{"name":"dougb","email":"a371e9dfd068c35ca8d4555b05d2c2e304b2ce59@FreeBSD.org"},"sha":"b450ecae876778c8c829eb82917febc7aac74ce4","message":"Upgrade to BIND 9.8.1-P1 to address the following DDOS bug:\n\nRecursive name servers are failing with an assertion:\nINSIST(! dns_rdataset_isassociated(sigrdataset))\n\nAt this time it is not thought that authoritative-only servers\nare affected, but information about this bug is evolving rapidly.\n\nBecause it may be possible to trigger this bug even on networks\nthat do not allow untrusted users to access the recursive name\nservers (perhaps via specially crafted e-mail messages, and/or\nmalicious web sites) it is recommended that ALL operators of\nrecursive name servers upgrade immediately.\n\nFor more information see:\nhttps://www.isc.org/software/bind/advisories/cve-2011-tbd\nwhich will be updated as more information becomes available.\n\nhttps://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4313","url":"https://api.github.com/repos/freebsd/freebsd/commits/b450ecae876778c8c829eb82917febc7aac74ce4"},{"author":{"name":"davidxu","email":"71ff1139e39d4cad34c7e5d9267b15b84da21141@FreeBSD.org"},"sha":"82bfc7f7d27040e117214df5f9a5097fb9260c96","message":"Pass CVWAIT flags to kernel, this should handle\ntimeout correctly for pthread_cond_timedwait when\nit uses kernel-based condition variable.\n\nPR:\t162403\nSubmitted by: jilles\nMFC after: 3 days","url":"https://api.github.com/repos/freebsd/freebsd/commits/82bfc7f7d27040e117214df5f9a5097fb9260c96"}],"ref":"refs/heads/user/attilio/vmcontention","head":"8a2ffb67f8d73d79bb1c6a611e2b3ebb1c144313","push_id":50522511,"size":51}