All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: rolandtollenaar@domain.hid
Cc: Xenomai-help@domain.hid,
	EML users <ethercatmaster-users@domain.hid>,
	rtnet-users <rtnet-users@domain.hid>
Subject: Re: [Xenomai-help] [Ethercatmaster-users] EML conflict with RTCAN? low_level_input	framebuilding failed.
Date: Mon, 13 Aug 2007 20:30:10 +0200	[thread overview]
Message-ID: <46C0A332.2040701@domain.hid> (raw)
In-Reply-To: <46C0A02A.1010706@domain.hid>

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

Roland Tollenaar wrote:
> Hi,
> 
>>> The 64 is a value I got from the mailing list. How large can I make this
>>> and what am I compromising?
>>
>> Each buffer is slightly more than 1.5 KB heavy. Do your maths :). How
>> many buffers you need depend on how many incoming and outgoing frames
>> might be queued into they are processed. And that depends on the frame

s/into/until/ (my brain-based dictionary must be broken)

>> rate and the time your EML stack has to handle it in the worst case. I
>> can't give you numbers on this, that depends on _your_ setup.
> 
> That much is clear. Will make it big out of shear inability to
> calculate. The lost memory is of almost no concern.

Just make sure that picking an arbitrary large pool size doesn't paper
over some real system design issue that may manifests in huge latencies.
Again, I don't know your numbers, so I cannot tell what is reasonable
and what an indication of a problem. A system-level analysis of the
event flows would be a good job for LTTng now - if it only worked already...

Jan


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]

  reply	other threads:[~2007-08-13 18:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-13  9:45 [Xenomai-help] EML conflict with RTCAN? low_level_input framebuilding failed Roland Tollenaar
2007-08-13 11:41 ` Wolfgang Grandegger
2007-08-13 12:41   ` Roland Tollenaar
2007-08-13 13:03     ` Wolfgang Grandegger
2007-08-13 13:11       ` Roland Tollenaar
2007-08-13 14:00       ` Roland Tollenaar
2007-08-13 14:51         ` [Xenomai-help] [Ethercatmaster-users] " Jan Kiszka
2007-08-13 15:55           ` Roland Tollenaar
2007-08-13 16:57             ` Jan Kiszka
2007-08-13 17:40               ` Roland Tollenaar
2007-08-13 17:57                 ` Jan Kiszka
2007-08-13 18:17                   ` Roland Tollenaar
2007-08-13 18:30                     ` Jan Kiszka [this message]
2007-08-14 13:56           ` Roland Tollenaar
2007-08-14 14:47             ` Klaas Gadeyne
2007-08-14 18:03               ` Roland Tollenaar
2007-08-14 19:17                 ` Jan Kiszka
2007-08-15  6:11                   ` Roland Tollenaar
2007-08-15  8:24                     ` Jan Kiszka
2007-08-15  8:37                       ` Roland Tollenaar
2007-08-15  9:50                       ` Roland Tollenaar
2007-08-15 10:30                         ` Wolfgang Grandegger
2007-08-15 10:30                           ` Roland Tollenaar

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=46C0A332.2040701@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=Xenomai-help@domain.hid \
    --cc=ethercatmaster-users@domain.hid \
    --cc=rolandtollenaar@domain.hid \
    --cc=rtnet-users@domain.hid \
    /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.