From: brian <knotwurk@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] increase pipe size/buffers/atomicity :D
Date: Wed, 7 Apr 2010 19:38:32 -0600 [thread overview]
Message-ID: <x2sb985fb501004071838z51a832dftdfaece15e5a0e154@mail.gmail.com> (raw)
(tested and working with 2.6.32.8 kernel, on a Athlon/686)
--- include/linux/pipe_fs_i.h.orig 2010-04-06 22:56:51.000000000 -0500
+++ include/linux/pipe_fs_i.h 2010-04-06 22:56:58.000000000 -0500
@@ -3,7 +3,7 @@
#define PIPEFS_MAGIC 0x50495045
-#define PIPE_BUFFERS (16)
+#define PIPE_BUFFERS (32)
#define PIPE_BUF_FLAG_LRU 0x01 /* page is on the LRU */
#define PIPE_BUF_FLAG_ATOMIC 0x02 /* was atomically mapped */
--- include/asm-generic/page.h.orig 2010-04-06 22:57:08.000000000 -0500
+++ include/asm-generic/page.h 2010-04-06 22:57:23.000000000 -0500
@@ -12,7 +12,7 @@
/* PAGE_SHIFT determines the page size */
-#define PAGE_SHIFT 12
+#define PAGE_SHIFT 13
#ifdef __ASSEMBLY__
#define PAGE_SIZE (1 << PAGE_SHIFT)
#else
--- include/linux/limits.h.orig 2010-04-06 22:54:15.000000000 -0500
+++ include/linux/limits.h 2010-04-06 22:56:28.000000000 -0500
@@ -10,7 +10,7 @@
#define MAX_INPUT 255 /* size of the type-ahead buffer */
#define NAME_MAX 255 /* # chars in a file name */
#define PATH_MAX 4096 /* # chars in a path name including nul */
-#define PIPE_BUF 4096 /* # bytes in atomic write to a pipe */
+#define PIPE_BUF 8192 /* # bytes in atomic write to a pipe */
#define XATTR_NAME_MAX 255 /* # chars in an extended attribute name */
#define XATTR_SIZE_MAX 65536 /* size of an extended attribute value (64k) */
#define XATTR_LIST_MAX 65536 /* size of extended attribute namelist (64k) */
next reply other threads:[~2010-04-08 1:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-08 1:38 brian [this message]
2010-04-08 5:11 ` [PATCH] increase pipe size/buffers/atomicity :D Eric Dumazet
2010-04-08 15:14 ` Steven J. Magnani
2010-04-09 19:50 ` Brian Haslett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=x2sb985fb501004071838z51a832dftdfaece15e5a0e154@mail.gmail.com \
--to=knotwurk@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).