All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bezdeka, Florian" <florian.bezdeka@siemens.com>
To: "xenomai@xenomai.org" <xenomai@xenomai.org>,
	"jan.kiszka@siemens.com" <jan.kiszka@siemens.com>
Subject: Re: [RFC PATCH 0/4] Export mqueues to procfs
Date: Wed, 18 Aug 2021 12:02:34 +0000	[thread overview]
Message-ID: <f39f1a03038611bae129ba76e14fcc8a75847634.camel@siemens.com> (raw)
In-Reply-To: <88684359-fe65-3f5a-362c-a5dd30584860@siemens.com>

On Wed, 2021-08-18 at 13:41 +0200, Jan Kiszka wrote:
> On 18.08.21 13:24, Florian Bezdeka wrote:
> > Hi,
> > 
> > this is another try to make registered mqueues visible. This time by
> > exporting them to the procfs, namely to
> > /proc/xenomai/registry/mqueue/<name>
> > 
> > Let me know what you think... 
> > 
> > I had to rework the existing export machinery a bit to get rid of the so
> > called "root" directory which is normally created. See patch
> > descriptions for details.
> > 
> > Best regards,
> > Florian
> > 
> > Florian Bezdeka (4):
> >   cobalt/registry: Make the root directory for proc exports optional
> >   cobalt/registry: Share xnregistry_vfreg_ops with other compile units
> >   cobalt/registry: Initialize refcnt of exported virtual proc files
> >   cobalt/mqueue: Export created mqueues to procfs
> > 
> >  include/cobalt/kernel/registry.h |  2 ++
> >  kernel/cobalt/posix/mqueue.c     | 35 +++++++++++++++++++++++++++++++-
> >  kernel/cobalt/registry.c         | 13 ++++++------
> >  3 files changed, 43 insertions(+), 7 deletions(-)
> > 
> 
> Will have a look.
> 
> We likely then also want the same for pshared semaphores, right?
> Anything else that could get a name (which may collide or become orphaned)?

Yes, to be complete we should do the same for shared semaphores. 

The previously submitted "dump patch" handled all registered types
(mqueue, semaphore, ...) the same way. But there was no type
information available. The registry holds the keys only.

> 
> Jan
> 


      reply	other threads:[~2021-08-18 12:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-18 11:24 [RFC PATCH 0/4] Export mqueues to procfs Florian Bezdeka
2021-08-18 11:24 ` [RFC PATCH 1/4] cobalt/registry: Make the root directory for proc exports optional Florian Bezdeka
2021-08-18 13:26   ` Philippe Gerum
2021-08-18 13:33     ` Bezdeka, Florian
2021-08-18 14:02       ` Philippe Gerum
2021-08-18 14:11         ` Bezdeka, Florian
2021-08-18 14:13           ` Jan Kiszka
2021-08-18 14:31             ` Philippe Gerum
2021-08-18 11:24 ` [RFC PATCH 2/4] cobalt/registry: Share xnregistry_vfreg_ops with other compile units Florian Bezdeka
2021-08-18 11:24 ` [RFC PATCH 3/4] cobalt/registry: Initialize refcnt of exported virtual proc files Florian Bezdeka
2021-08-18 11:24 ` [RFC PATCH 4/4] cobalt/mqueue: Export created mqueues to procfs Florian Bezdeka
2021-08-18 11:41 ` [RFC PATCH 0/4] Export " Jan Kiszka
2021-08-18 12:02   ` Bezdeka, Florian [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=f39f1a03038611bae129ba76e14fcc8a75847634.camel@siemens.com \
    --to=florian.bezdeka@siemens.com \
    --cc=jan.kiszka@siemens.com \
    --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.