From: Andi Kleen <ak@suse.de>
To: Martin Peschke <mp3@de.ibm.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/6] statistics infrastructure - prerequisite: scatter-gather ringbuffer
Date: 14 Dec 2005 19:32:28 +0100 [thread overview]
Message-ID: <p73d5jz8r7n.fsf@verdi.suse.de> (raw)
In-Reply-To: <43A044AA.4040103@de.ibm.com>
Martin Peschke <mp3@de.ibm.com> writes:
> [patch 1/6] statistics infrastructure - prerequisite: scatter-gather ringbuffer
>
> This patch implemenents a ringbuffer made up of scattered memory (pages).
> The current implementation allows fixed-size entries to be stored in the
> ringbuffer. There are routines that simplify writing entries to a buffer
> and reading entries from a buffer. Ringbuffer resizing is not supported, yet.
>
> This is actually a separate feature which could be used for purposes
> other than statistics.
This seems redundant with relayfs.
-Andi
next prev parent reply other threads:[~2005-12-14 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-14 16:13 [patch 1/6] statistics infrastructure - prerequisite: scatter-gather ringbuffer Martin Peschke
2005-12-14 18:32 ` Andi Kleen [this message]
2005-12-15 2:35 ` Martin Peschke
2005-12-15 3:33 ` Andi Kleen
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=p73d5jz8r7n.fsf@verdi.suse.de \
--to=ak@suse.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mp3@de.ibm.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;
as well as URLs for NNTP newsgroup(s).