All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Stéphane ANCELOT" <sancelot@free.fr>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] rt_e1000e driver issues
Date: Tue, 1 Sep 2015 12:20:01 +0200	[thread overview]
Message-ID: <20150901102001.GB26674@hermes.click-hack.org> (raw)
In-Reply-To: <20150831183003.GA5696@hermes.click-hack.org>

On Mon, Aug 31, 2015 at 08:30:03PM +0200, Gilles Chanteperdrix wrote:
> On Mon, Aug 31, 2015 at 04:04:18PM +0200, Stéphane ANCELOT wrote:
> > Hi,
> > 
> > I am checking timing issues of realtime rtnet frames in my application.
> > Timing to send a frame is  convenient.
> > but I have some issues with the time to receive the frames.
> > 
> > Although the RxDelays are cleared, the frame is received almost 175us later
> > than it should in comparison with a rt8169 driver (v2.6 version) and the
> > same application.
> > 
> > Any idea where to look at first ?
> 
> modinfo rt_e1000e

Actually, the module parameters are the same as the Linux driver,
so, they are documented in Documentation/networking/e1000e.txt in
the Linux kernel sources, here for instance:
https://git.xenomai.org/ipipe.git/tree/Documentation/networking/e1000e.txt?id=v4.2-rc1
(beware that the driver versions are not the same, so, there may be
some differences, like default values, or even some options, but
modinfo will tell you that).

Your problem is probably that you should disable interrupt
throttling passing InterruptThrottleRate=0.

-- 
					    Gilles.
https://click-hack.org


  reply	other threads:[~2015-09-01 10:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 14:04 [Xenomai] rt_e1000e driver issues Stéphane ANCELOT
2015-08-31 18:30 ` Gilles Chanteperdrix
2015-09-01 10:20   ` Gilles Chanteperdrix [this message]
2015-09-02 14:00     ` Stéphane ANCELOT
2015-09-02 14:09       ` Gilles Chanteperdrix

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=20150901102001.GB26674@hermes.click-hack.org \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=sancelot@free.fr \
    --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.