From: Philippe Gerum <rpm@xenomai.org>
To: Steve B <sbattazzo@gmail.com>, xenomai <xenomai@xenomai.org>
Subject: Re: [Xenomai] XDDP socket, any memory allocation when sendto() is called?
Date: Fri, 13 May 2016 15:50:15 +0200 [thread overview]
Message-ID: <5735DB97.5080804@xenomai.org> (raw)
In-Reply-To: <CAEMXjGyohbJkCzMDTGWfhbREdmbT7VWoHpinyvbLTdpyRkEw1Q@mail.gmail.com>
On 05/13/2016 01:42 AM, Steve B wrote:
> Hi guys,
> Does sendto() going into an XDDP socket involve any memory allocation
> that's not automatically getting de-allocated each time it's called?
>
> I have an application running where I am writing a few different types of
> data packets to an XDDP socket on a fixed periodic basis, and in a separate
> console using "free" I see the memory usage increasing steadily until I
> only have about 5MB left, at which point it doesn't grow/shrink anymore. I
> don't seem to be losing any data after this happens, though.
>
> I tried temporarily disabling my largest packet type, and saw that the rate
> of memory consumption decreases very significantly, which is why I think it
> has something to do with this.
>
> I may be able to live with this if it's not causing any real problems but
> it is a little unsettling...
The memory is freed upon read() on the other side. Do the datagrams
linger somehow on the (non-rt) read-side?
--
Philippe.
next prev parent reply other threads:[~2016-05-13 13:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-12 23:42 [Xenomai] XDDP socket, any memory allocation when sendto() is called? Steve B
2016-05-13 13:50 ` Philippe Gerum [this message]
2016-05-13 17:53 ` Steve B
2016-05-13 18:08 ` Philippe Gerum
2016-05-13 18:19 ` Steve B
2016-05-13 18:27 ` Steve B
2016-05-13 18:45 ` Philippe Gerum
2016-05-13 19:42 ` Steve B
2016-05-14 12:28 ` Gilles Chanteperdrix
2016-05-14 13:00 ` Philippe Gerum
2016-05-17 0:17 ` Steve B
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=5735DB97.5080804@xenomai.org \
--to=rpm@xenomai.org \
--cc=sbattazzo@gmail.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.