From: Andi Kleen <ak@muc.de>
To: Tom Zanussi <zanussi@us.ibm.com>
Cc: Greg KH <greg@kroah.com>, Andrew Morton <akpm@osdl.org>,
Roman Zippel <zippel@linux-m68k.org>,
Robert Wisniewski <bob@watson.ibm.com>,
Tim Bird <tim.bird@AM.SONY.COM>,
karim@opersys.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] relayfs redux, part 2
Date: Sat, 29 Jan 2005 09:08:14 +0100 [thread overview]
Message-ID: <m1d5volksx.fsf@muc.de> (raw)
In-Reply-To: <16890.38062.477373.644205@tut.ibm.com> (Tom Zanussi's message of "Fri, 28 Jan 2005 13:38:22 -0600")
Tom Zanussi <zanussi@us.ibm.com> writes:
> Hi,
>
> This patch is the result of the latest round of liposuction on relayfs
> - the patch size is now 44K, down from 110K and the 200K before that.
> I'm posting it as a patch against 2.6.10 rather than -mm in order to
> make it easier to review, but will create one for -mm once the changes
> have settled down.
The logging fast path seems still a bit slow to me. I would like
to have a logging macro that is not much worse than a stdio putc,
basically something like
get_cpu();
if (buffer space > N) {
memcpy(buffer, input, N);
buffer pointer += N;
} else {
FreeBuffer(input, N);
}
put_cpu();
This would need interrupt protection only if interrupts can access
it, best you use separate buffers for that too.
-Andi
next prev parent reply other threads:[~2005-01-29 8:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-28 19:38 [PATCH] relayfs redux, part 2 Tom Zanussi
2005-01-28 20:48 ` Tim Bird
2005-01-28 22:24 ` Andrew Morton
2005-01-29 8:08 ` Andi Kleen [this message]
2005-01-30 4:58 ` Tom Zanussi
2005-01-31 12:57 ` Andi Kleen
2005-01-31 16:26 ` Tom Zanussi
2005-01-31 19:41 ` Karim Yaghmour
2005-01-31 21:03 ` Tom Zanussi
2005-01-31 21:12 ` Karim Yaghmour
2005-01-31 19:38 ` Karim Yaghmour
2005-01-29 8:15 ` Greg KH
2005-01-30 5:02 ` Tom Zanussi
2005-01-31 22:10 ` Karim Yaghmour
2005-01-31 22:33 ` Greg KH
2005-01-31 22:35 ` Karim Yaghmour
2005-01-31 23:12 ` Roman Zippel
2005-02-01 15:44 ` Tom Zanussi
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=m1d5volksx.fsf@muc.de \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=bob@watson.ibm.com \
--cc=greg@kroah.com \
--cc=karim@opersys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tim.bird@AM.SONY.COM \
--cc=zanussi@us.ibm.com \
--cc=zippel@linux-m68k.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