- Sort Score
- Result 10 results
- Languages All
Results 1 - 10 of 70 for Madvise (0.25 sec)
-
docs/tuning/tuned.conf
[main] summary=Maximum server performance for MinIO [vm] transparent_hugepage=madvise [sysfs] /sys/kernel/mm/transparent_hugepage/defrag=defer+madvise /sys/kernel/mm/transparent_hugepage/khugepaged/max_ptes_none=0 [cpu] force_latency=1 governor=performance energy_perf_bias=performance min_perf_pct=100 [sysctl] fs.xfs.xfssyncd_centisecs=72000 net.core.busy_read=50 net.core.busy_poll=50 kernel.numa_balancing=1
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Fri Jul 12 23:31:18 UTC 2024 - 1.9K bytes - Viewed (0) -
guava/src/com/google/common/io/ByteStreams.java
* between paging memory and killing other processes - so allocating a gigantic buffer and * then sequentially accessing it could result in other processes dying. This is solvable * via madvise(2), but that obviously doesn't exist in java. * <li>Ordinary copy. Kernel copies bytes into a kernel buffer, from a kernel buffer into a * userspace buffer (byte[] or ByteBuffer), then copies them from that buffer into the
Registered: Fri Nov 01 12:43:10 UTC 2024 - Last Modified: Sat Oct 19 00:26:48 UTC 2024 - 29.7K bytes - Viewed (0) -
licenses/golang.org/x/net/LICENSE
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Fri Aug 16 01:35:47 UTC 2024 - 1.4K bytes - Viewed (0) -
licenses/github.com/sagikazarmark/slog-shim/LICENSE
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Tue Nov 28 01:47:28 UTC 2023 - 1.4K bytes - Viewed (0) -
licenses/github.com/prometheus/client_golang/internal/github.com/golang/gddo/LICENSE
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Fri Aug 16 01:35:47 UTC 2024 - 1.4K bytes - Viewed (0) -
licenses/golang.org/x/sys/LICENSE
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Fri Aug 16 01:35:47 UTC 2024 - 1.4K bytes - Viewed (0) -
licenses/golang.org/x/term/LICENSE
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Fri Aug 16 01:35:47 UTC 2024 - 1.4K bytes - Viewed (0) -
licenses/github.com/go-jose/go-jose/v4/json/LICENSE
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
Registered: Wed Nov 06 22:53:10 UTC 2024 - Last Modified: Mon Apr 08 17:05:56 UTC 2024 - 1.4K bytes - Viewed (0) -
impl/maven-core/src/main/java/org/apache/maven/eventspy/EventSpy.java
* looks up all implementers of this interface and calls their {@link #init(Context)} method. Note: * Implementors are strongly advised to inherit from {@link AbstractEventSpy} instead of directly implementing this * interface. * @since 3.0.2 */ public interface EventSpy { /** * Context */ interface Context {
Registered: Sun Nov 03 03:35:11 UTC 2024 - Last Modified: Fri Oct 25 12:31:46 UTC 2024 - 2.6K bytes - Viewed (0) -
docs/hotfixes.md
This is due to an issue of prefix based Matcher() function which was incorrectly matching prefix based on resource prefixes instead of exact match. ``` - There is always a possibility of a fix that is new, it is advised that the developer must make sure that the fix is sent upstream, reviewed and merged to the master branch. ## Creating a hotfix branch
Registered: Sun Nov 03 19:28:11 UTC 2024 - Last Modified: Wed Feb 14 21:36:02 UTC 2024 - 5K bytes - Viewed (0)