From: "Paul Menage" <menage@google.com>
To: "Paul Jackson" <pj@sgi.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Allow a larger buffer for writes to cpuset files
Date: Mon, 30 Oct 2006 20:15:11 -0800 [thread overview]
Message-ID: <6599ad830610302015r473bee49pd8c0381a1ca04742@mail.gmail.com> (raw)
In-Reply-To: <20061030200053.f9836cce.pj@sgi.com>
On 10/30/06, Paul Jackson <pj@sgi.com> wrote:
>
> How about coding for the possibility that either NR_CPUS or MAX_NUMNODES
> is larger, and removing 'cpu' from the comment:
>
> /* Crude upper limit on largest legitimate list user might write. */
> if (nbytes > 100 + 6 * max(NR_CPUS, MAX_NUMNODES))
>
Yes, that does seem like a better idea.
Paul
prev parent reply other threads:[~2006-10-31 4:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 2:38 Paul Menage
2006-10-31 4:00 ` Paul Jackson
2006-10-31 4:15 ` Paul Menage [this message]
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=6599ad830610302015r473bee49pd8c0381a1ca04742@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pj@sgi.com \
/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
all inboxes | Powered by JetHome®