From: Linus Torvalds <torvalds@linux-foundation.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
prasad@linux.vnet.ibm.com,
Mathieu Desnoyers <compudj@krystal.dyndns.org>,
"Frank Ch. Eigler" <fche@redhat.com>,
David Wilder <dwilder@us.ibm.com>,
hch@lst.de, Martin Bligh <mbligh@google.com>,
Christoph Hellwig <hch@infradead.org>,
Steven Rostedt <srostedt@redhat.com>
Subject: Re: [RFC PATCH 1/2 v2] Unified trace buffer
Date: Thu, 25 Sep 2008 10:25:00 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.1.10.0809251023090.3265@nehalem.linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0809251312010.27920@gandalf.stny.rr.com>
On Thu, 25 Sep 2008, Steven Rostedt wrote:
>
> The problem with this is overwrite mode, which is the only mode ftace
> currently offers. What happens when your writer starts overwriting the
> ring buffer and there is no reader?
Overwrite things on page at a time. Don't you already do that? (I didn't
check that closely, I just assumed you would do the _much_ simpler "move
the head to the next page" thing rather than trying to mix head and tail
on the same page.
> What happens is that the start value is gone. You do not have a way to use
> all the deltas to catch up to the remaining events.
Use the page start date for the first event in a page. But within pages,
make everything depend on previous event.
Linus
next prev parent reply other threads:[~2008-09-25 17:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-25 15:58 [RFC PATCH 0/2 v2] Unified trace buffer (take two) Steven Rostedt
2008-09-25 15:58 ` [RFC PATCH 1/2 v2] Unified trace buffer Steven Rostedt
2008-09-25 17:02 ` Linus Torvalds
2008-09-25 17:16 ` Steven Rostedt
2008-09-25 17:25 ` Linus Torvalds [this message]
2008-09-25 17:46 ` Steven Rostedt
2008-09-25 17:35 ` Mathieu Desnoyers
2008-09-25 17:48 ` Steven Rostedt
2008-09-25 18:25 ` Mathieu Desnoyers
2008-09-25 15:58 ` [RFC PATCH 2/2 v2] ftrace: make work with new ring buffer Steven Rostedt
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=alpine.LFD.1.10.0809251023090.3265@nehalem.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=compudj@krystal.dyndns.org \
--cc=dwilder@us.ibm.com \
--cc=fche@redhat.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=prasad@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=srostedt@redhat.com \
--cc=tglx@linutronix.de \
/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.