All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@domain.hid>
To: Robin Walser <robinwalser45@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-core] Socket Buffer overflow
Date: Wed, 21 Mar 2007 22:43:29 +0100	[thread overview]
Message-ID: <4601A701.6070802@domain.hid> (raw)
In-Reply-To: <4601A451.7090408@domain.hid>

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

Robin Walser wrote:
> 
>> Are you using RT-Socket-CAN? Could you please provide more detailed
>> information like what is the returned error code and are there kernel
>> log messages (visible with $ dmsg)?
>>
>> Wolfgang.
> My programm based on frag-ip:
> http://www.rts.uni-hannover.de/rtnet/lxr/source//examples/xenomai/native/frag-ip.c

[Hmm, might be tricky to tell apart, but this is now an example for a
RTnet-specific question => rtnet-user list. If it wasn't, xenomai-help
would have been the preferred place for support requests.]

> 
> I use RTnet. The returned error code is always -115 and I have no kernel
> log messages.
> I think, I'm only need a buffer status report. Is this available?

Are you sure it's 115? Anyway, buffer overflows can happen if you sent
out frames at a higher rate than hardware can handle. Throttle your
transmission, at least once that error pops up.

But what is your desired transmission rate after all? Why not set up a
periodic transmission task, either waiting for timer events or on the
RTmac/TDMA cycle (if you use TDMA with RTnet)?

Jan


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

      reply	other threads:[~2007-03-21 21:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-21 20:13 [Xenomai-core] Socket Buffer overflow Robin Walser
2007-03-21 20:44 ` Wolfgang Grandegger
2007-03-21 21:32   ` Robin Walser
2007-03-21 21:43     ` Jan Kiszka [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=4601A701.6070802@domain.hid \
    --to=jan.kiszka@domain.hid \
    --cc=robinwalser45@domain.hid \
    --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.