From: Greg KH <greg@kroah.com>
To: Alan Cox <alan@linux.intel.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tty: Keep the default buffering to sub-page units
Date: Wed, 17 Feb 2010 15:11:41 -0800 [thread overview]
Message-ID: <20100217231141.GA4734@kroah.com> (raw)
In-Reply-To: <20100217130405.15830.27197.stgit@localhost.localdomain>
On Wed, Feb 17, 2010 at 01:04:53PM +0000, Alan Cox wrote:
> We allocate during interrupts so while our buffering is normally diced up
> small anyway on some hardware at speed we can pressure the VM excessively
> for page pairs. We don't really need big buffers to be linear so don't try
> so hard.
>
> In order to make this work well we will tidy up excess callers to request_room,
> which cannot itself enforce this break up.
>
> Signed-off-by: Alan Cox <alan@linux.intel.com>
> ---
>
> drivers/char/tty_buffer.c | 5 +++--
> include/linux/tty.h | 10 ++++++++++
> 2 files changed, 13 insertions(+), 2 deletions(-)
>
>
> diff --git a/drivers/char/tty_buffer.c b/drivers/char/tty_buffer.c
> index 66fa4e1..8402eda 100644
> --- a/drivers/char/tty_buffer.c
> +++ b/drivers/char/tty_buffer.c
> @@ -247,7 +247,7 @@ int tty_insert_flip_string(struct tty_struct *tty, const unsigned char *chars,
> {
> int copied = 0;
> do {
> - int space = tty_buffer_request_room(tty, size - copied);
> + int space = tty_buffer_request_room(tty, goal);
This causes the build error:
CC drivers/char/tty_buffer.o
drivers/char/tty_buffer.c: In function ‘tty_insert_flip_string’:
drivers/char/tty_buffer.c:250: error: ‘goal’ undeclared (first use in this function)
drivers/char/tty_buffer.c:250: error: (Each undeclared identifier is reported only once
drivers/char/tty_buffer.c:250: error: for each function it appears in.)
So I'll drop it for now.
Care to fix this?
thanks,
greg k-h
prev parent reply other threads:[~2010-02-17 23:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-17 13:04 [PATCH] tty: Keep the default buffering to sub-page units Alan Cox
2010-02-17 23:11 ` Greg KH [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=20100217231141.GA4734@kroah.com \
--to=greg@kroah.com \
--cc=alan@linux.intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.