All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Freyder <steve@freyder.net>
To: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: [Xenomai] Queue status files/FUSE issue -- part two
Date: Mon, 16 Apr 2018 14:25:28 -0500	[thread overview]
Message-ID: <5AD4F8A8.70604@freyder.net> (raw)

Greetings again,

There seems to be an issue with the RT queue status file formatting and 
perhaps
the way in which the [WAITERS] list is managed, and/or maybe the way the 
output
string termination is done.

I can't be sure and thought I should simply submit the test 
program/scripts and
document the results.  I am attaching them as a compressed tar file, I hope
that is acceptable form for the forum.

I noticed that the 32768 length in this area of the code:

./xenomai-3/lib/copperplate/registry.c-317-             case O_RDWR:
./xenomai-3/lib/copperplate/registry.c-318- sbuf->st_mode |= 0666;
./xenomai-3/lib/copperplate/registry.c-319- break;
./xenomai-3/lib/copperplate/registry.c-320-             }
./xenomai-3/lib/copperplate/registry.c-321- sbuf->st_nlink = 1;
./xenomai-3/lib/copperplate/registry.c:322: sbuf->st_size = 32768; /* 
XXX: this should be dynamic. */
./xenomai-3/lib/copperplate/registry.c-323- sbuf->st_atim = fsobj->mtime;
./xenomai-3/lib/copperplate/registry.c-324- sbuf->st_ctim = fsobj->ctime;
./xenomai-3/lib/copperplate/registry.c-325- sbuf->st_mtim = fsobj->mtime;

sometimes is altered, before the FUSE read request is satisfied, and
sometimes not.  I didn't try to trace it too far.

The script "qtest.sh" runs a program called "qx" (Queue eXerciser) to 
create a
queue, and post a read on the queue.  Two copies are launched in the 
background
then the first is killed.  The queue status file is displayed in the 
process.

Note what happens to the queue status output as you run "sh qtest.sh"
repeatedly.  On my system, I see something like what is shown below.

The included "killtask.sh" can be used to get rid of all of the 
lingering tasks
after the testing is over.

I use a lingering sysregd launched in sr.sh before starting
the testing, looks like this:

sysregd --daemon --root /var/run/xenomai/root/sess --linger

Thanks in advance,
Steve


------------------------------------------------------------------------
# sh qtest.sh
+ t1=15342
+ sleep 1
+ qx q foo r
15342:rt_queue_read(&q,buf,512,TM_INFINITE)...[unfinished]
+ t2=15348
+ kill 15342
+ qx q foo r
+ sleep 1
15348:rt_queue_read(&q,buf,512,TM_INFINITE)...[unfinished]
qtest.sh: line 10: 15342 Terminated              qx q foo r
+ qstat foo
cat /run/xenomai/root/sess/15348/alchemy/queues/foo
-------------------
[TYPE]  [TOTALMEM]  [USEDMEM]  [QLIMIT]  [MCOUNT]
  FIFO        8704          0         0         0
--
[WAITER]
task@1[15348]

-------------------
# sh qtest.sh
+ t1=15359
+ sleep 1
+ qx q foo r
15359:rt_queue_read(&q,buf,512,TM_INFINITE)...[unfinished]
+ t2=15364
+ kill 15359
+ sleep 1
+ qx q foo r
15364:rt_queue_read(&q,buf,512,TM_INFINITE)...[unfinished]
qtest.sh: line 10: 15359 Terminated              qx q foo r
+ qstat foo
cat /run/xenomai/root/sess/15348/alchemy/queues/foo
-------------------
[TYPE]  [TOTALMEM]  [USEDMEM]  [QLIMIT]  [MCOUNT]
  FIFO        8704          0         0         0
--
[WAITER]
task@1[15348]
task@1[15359]
task@1[15364]
  FIFO        8704          0         0         0
--
[W-------------------
# sh qtest.sh
+ t1=15377
+ sleep 1
+ qx q foo r
15377:rt_queue_read(&q,buf,512,TM_INFINITE)...[unfinished]
+ t2=15382
+ kill 15377
+ sleep 1
+ qx q foo r
15382:rt_queue_read(&q,buf,512,TM_INFINITE)...[unfinished]
qtest.sh: line 10: 15377 Terminated              qx q foo r
+ qstat foo
cat /run/xenomai/root/sess/15348/alchemy/queues/foo
-------------------
[TYPE]  [TOTALMEM]  [USEDMEM]  [QLIMIT]  [MCOUNT]
  FIFO        8704          0         0         0
--
[WAITER]
task@1[15348]
task@1[15359]
task@1[15364]
task@1[15377]
task@1[15382]
          0         0
--
[WAITER]
task@1[15348]
task@1[15359]
task@1[15364]
  FIFO        87-------------------
# sh qtest.sh
+ t1=15393
+ sleep 1
+ qx q foo r
15393:rt_queue_read(&q,buf,512,TM_INFINITE)...[unfinished]
+ t2=15398
+ kill 15393
+ sleep 1
+ qx q foo r
15398:rt_queue_read(&q,buf,512,TM_INFINITE)...[unfinished]
qtest.sh: line 10: 15393 Terminated              qx q foo r
+ qstat foo
cat /run/xenomai/root/sess/15348/alchemy/queues/foo
-------------------
[TYPE]  [TOTALMEM]  [USEDMEM]  [QLIMIT]  [MCOUNT]
  FIFO        8704          0         0         0
--
[WAITER]
task@1[15348]
task@1[15359]
task@1[15364]
task@1[15377]
task@1[15382]
task@1[15393]
task@1[15398]
TER]
task@1[15348]
task@1[15359]
task@1[15364]
task@1[15377]
task@1[15382]
          0         0
--
[WAITER]
task@1[15348]
task-------------------

-------------- next part --------------
A non-text attachment was scrubbed...
Name: queue-status.tar.gz
Type: application/x-gzip
Size: 84280 bytes
Desc: not available
URL: <http://xenomai.org/pipermail/xenomai/attachments/20180416/26d4f6df/attachment.bin>

             reply	other threads:[~2018-04-16 19:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-16 19:25 Steve Freyder [this message]
2018-06-14 16:45 ` [Xenomai] Queue status files/FUSE issue -- part two Philippe Gerum
2018-06-14 18:19   ` Steve Freyder
2018-06-14 19:05     ` Philippe Gerum
2018-06-14 21:52       ` Steve Freyder

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=5AD4F8A8.70604@freyder.net \
    --to=steve@freyder.net \
    --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.