public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] Changing vis output ready for mainline...
Date: Tue, 13 Oct 2009 00:48:49 +0800	[thread overview]
Message-ID: <200910130048.49571.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20091012081122.GB12833@lunn.ch>


Hi,

> 1) No other /proc file in mainline does any special formatting. Either
> comma separated value or space separated value is used. User space
> reads this and then performs any formatting needed.
> 
> 2) No other /proc file supports two userspace switchable formats!
> 
> 3) We have problems when multiple applications wants different formats
> at the same time. One wants dot the other wants JSON. Currently there
> is no locking, so something bad is going to happen.
> 
> What do others thing of this? Does anybody have a different proposal?

thanks a lot for summarizing the situation and pushing for a solution.

It seems we have to decide where we want to go with batctl. Until now batctl 
was not mandatory to operate the batman-adv kernel module. batctl extended the 
modules functionality and made things easier to configure but remained 
optional.

Personally, I like it a lot that way because it does not create unnecessary 
dependencies. It can become an uphill battle if you want to keep your kernel 
and its configuration tools in sync. Everyone that tried to use oprofile knows 
what I'm talking about (or the wireless tools to name another example).

So, the question is whether we want to make batctl the almighty tool that we 
always depend on or are we trying to find alternative solutions to avoid that 
dependency ?

One option for the case at hand might be debugfs 
(http://lwn.net/Articles/115282/). It is another filesystem which needs to be 
mounted seperately - there we can output whatever we want (unlike /proc). It 
would be possible to create virtual files for the dot draw / json / raw output 
(raw means the neutral format suggested by Andrew).

Soon we also will have to decide what to do with routing log as we can't 
"spam" the system log with our data. Again, debugfs seems like a good 
solution. That does not need to be decided now but could be a consistent path 
towards mainline integration.

Regards,
Marek

  parent reply	other threads:[~2009-10-12 16:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-12  8:11 [B.A.T.M.A.N.] Changing vis output ready for mainline Andrew Lunn
2009-10-12 11:59 ` Antoine van Gelder
2009-10-12 15:22   ` Andrew Lunn
2009-10-13  8:00   ` Andrew Lunn
2009-10-12 16:48 ` Marek Lindner [this message]
2009-10-12 21:36   ` elektra
2009-10-13  7:48   ` Andrew Lunn
2009-10-13  7:54 ` Andrew Lunn

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=200910130048.49571.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --cc=b.a.t.m.a.n@lists.open-mesh.net \
    /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