From: Leopold Palomo-Avellaneda <leo@alaxarxa.net>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Packaging Xenomai-3
Date: Mon, 26 Jan 2015 13:39:31 +0100 [thread overview]
Message-ID: <2052908.cWhQn5Pgch@soho> (raw)
In-Reply-To: <20150126120824.GF12812@hermes.click-hack.org>
El Dilluns, 26 de gener de 2015, a les 13:08:24, Gilles Chanteperdrix va
escriure:
> On Sun, Jan 25, 2015 at 07:43:21PM +0100, Leopold Palomo-Avellaneda wrote:
> > El Diumenge, 25 de gener de 2015, a les 19:10:16, Philippe Gerum va
escriure:
> > > On 01/25/2015 12:14 PM, Leopold Palomo-Avellaneda wrote:
> > > > But I was thinking in performance aspects comparing a system with
> > > > cobalt
> > > > vs a system with mercury.
> > >
> > > Yes, but the results are now outdated (2011). This said, such benchmark
> > > hardly reflected a use case. It was more a Xenomai 2.6.x vs 3.x analysis
> > > of basic mechanisms (event notification, serialization, buffer exchange
> > > etc) for measuring the impact of moving most of the real-time API
> > > implementation to user-space, only keeping the core resource management
> > > in kernel space. It proved to be positive.
> > >
> > > Mercury vs Cobalt was only a by-product of those tests, specifically on
> > > x86_32.
> >
> > After this thread, I think more firmly that the libs should be renamed in
> > the manner that they could be co-installed in the same root, standard
> > places.
> >
> > Please upstream, could you think about it?
>
> This is a decision that upstream should not impose to all users.
Interesting sentence. You are developing a new version with an step forward.
You have reworked libraries and for instance libxenomai, libnative, librtdm
doesn't exists in Xenomai-3. Also you have introduced new ones (libalchemy,
libcobalt, libcopperplate, libtrank.
You have developed xenomai in two main group of libraries (or use a cobalt
kernel or a mercury kernel) and are you saying that you cannot impose to all
users a suffix or something that the users could have both version co-
installed in standards places in their systems?
> Only users with your specific needs should do what you want.
Maybe I'm wrong. But after reading this thread I understood that to have a
kernel with both patches (i-pipe and preempt_rt) and, I understand, Xenomai-3
with the two versions could be a very interesting system to work on.
For instance, I'm in the robotics field, and after that mails I thought that
it could be a good solution that fit the cases where you have several loops,
with several rates with different importance.
> And
> in fact, I believe simply using the configure script options, it is
> possible to install libraries in different directories. Maybe even
> the --program* options apply to libraries too.
Not really. It's nice if you a have a package.
Leopold
--
--
Linux User 152692 GPG: 05F4A7A949A2D9AA
Catalonia
-------------------------------------
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://www.xenomai.org/pipermail/xenomai/attachments/20150126/f1f68980/attachment.sig>
next prev parent reply other threads:[~2015-01-26 12:39 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-23 12:09 [Xenomai] Packaging Xenomai-3 Leopold Palomo-Avellaneda
2015-01-23 15:52 ` Gilles Chanteperdrix
2015-01-23 16:50 ` Leopold Palomo-Avellaneda
2015-01-23 17:27 ` Gilles Chanteperdrix
2015-01-24 17:56 ` Leopold Palomo-Avellaneda
2015-01-25 9:14 ` Philippe Gerum
2015-01-25 11:14 ` Leopold Palomo-Avellaneda
2015-01-25 18:10 ` Philippe Gerum
2015-01-25 18:43 ` Leopold Palomo-Avellaneda
2015-01-26 12:08 ` Gilles Chanteperdrix
2015-01-26 12:39 ` Leopold Palomo-Avellaneda [this message]
2015-01-26 13:38 ` Daniele Nicolodi
2015-01-26 14:17 ` Leopold Palomo-Avellaneda
2015-01-26 14:24 ` Daniele Nicolodi
2015-01-26 14:01 ` Philippe Gerum
2015-01-26 14:47 ` Leopold Palomo-Avellaneda
2015-01-26 14:55 ` Gilles Chanteperdrix
2015-01-26 14:08 ` Gilles Chanteperdrix
2015-01-26 14:56 ` Leopold Palomo-Avellaneda
2015-01-26 14:59 ` Gilles Chanteperdrix
2015-01-26 17:46 ` Leopold Palomo-Avellaneda
2015-01-26 18:20 ` Gilles Chanteperdrix
2015-01-26 22:17 ` Leopold Palomo-Avellaneda
2015-01-26 22:26 ` Daniele Nicolodi
2015-01-26 22:57 ` Leopold Palomo-Avellaneda
2015-01-26 18:32 ` Gilles Chanteperdrix
2015-01-26 22:19 ` Leopold Palomo-Avellaneda
2015-01-23 16:04 ` Philippe Gerum
2015-01-23 17:02 ` Leopold Palomo-Avellaneda
2015-01-23 17:24 ` Philippe Gerum
2015-01-23 17:47 ` Gilles Chanteperdrix
2015-01-24 10:05 ` Philippe Gerum
2015-01-24 17:43 ` Leopold Palomo-Avellaneda
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=2052908.cWhQn5Pgch@soho \
--to=leo@alaxarxa.net \
--cc=gilles.chanteperdrix@xenomai.org \
--cc=xenomai@xenomai.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 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.