Mirror of the lttng-dev mailing list
 help / color / mirror / Atom feed
From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] sub roadmap for text output
Date: Fri, 26 Dec 2008 10:23:35 -0500	[thread overview]
Message-ID: <20081226152335.GA4016@Krystal> (raw)
In-Reply-To: <4954A8FF.7060702@cn.fujitsu.com>

* Lai Jiangshan (laijs at cn.fujitsu.com) wrote:
> Lai Jiangshan wrote:
> 
> > 2) ltt-relay events traveling
> >    current ltt-relay does not support iterator. it seems that ltt-relay is too
> >    complex to do this things. Is any plan to revise ltt-relay?
> > 
> 
> Hi, Mathieu Desnoyers
> 
> 	Merry Christmas!
> 
> 	I still don't know how to deal with corrupted data which is brought when
> subbuffer is pushed by the writer in the kernel. Any idea?
> The iterator is hard to be designed congruously with reserver side.
> 

Merry Christmas Lai,

Here is how to deal with it :

- Allow iterators only in the following cases :
  - non-overwrite channel
  - writing is stopped (paused) in overwrite channel

- _Never_ allow iterators on overwrite channels with non-paused writers.
  That's the only scenario which can corrupt a channel due to a writer
  push.

Best regards,

Mathieu

P.S. I'll be on vacation and probably unreachable until January 2nd.


> 	Thanks.
> Lai.
> 
> 
> _______________________________________________
> ltt-dev mailing list
> ltt-dev at lists.casi.polymtl.ca
> http://lists.casi.polymtl.ca/cgi-bin/mailman/listinfo/ltt-dev
> 

-- 
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F  BA06 3F25 A8FE 3BAE 9A68




      reply	other threads:[~2008-12-26 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-10  4:55 Lai Jiangshan
2008-12-10 12:22 ` Mathieu Desnoyers
2008-12-11  6:44   ` Lai Jiangshan
2008-12-26  9:50 ` Lai Jiangshan
2008-12-26 15:23   ` Mathieu Desnoyers [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=20081226152335.GA4016@Krystal \
    --to=compudj@krystal.dyndns.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