public inbox for linux-rt-users@vger.kernel.org
 help / color / mirror / Atom feed
From: "Nebojša Ćosić" <nebojsa@asnn.org>
To: Stanislav Meduna <stano@meduna.org>
Cc: "linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>
Subject: Re: e1000e 82574L transmit latency?
Date: Tue, 28 May 2013 16:09:07 +0200	[thread overview]
Message-ID: <20130528160907.2d98fc65@sth491dt.servo.net> (raw)
In-Reply-To: <51A4B5F9.6010206@meduna.org>

Дана Tue, 28 May 2013 15:49:45 +0200
Stanislav Meduna <stano@meduna.org> написа:

> On 28.05.2013 15:01, Nebojša Ćosić wrote:
> 
> > If you are having several processes/threads with different priorities
> > sending on same eth, combined with high cpu load on RT processes, than
> > it sounds a lot like a problem I had: Check
> > http://article.gmane.org/gmane.linux.rt.user/10163 for details
> 
> Hm, interesting. However, there is just one thread sending on the
> interface and all threads with higher priority generally only run for
> brief intervals and do not do anything with ethernet. There are
> lower-prio threads doing full TCP/IP but they communivate on another
> interface (also a e100e one).
> 
> Thanks
Well, I think it still applies. Lock which is responsible for this
problem is driver wise...
Lower prio thread can take driver lock, and thus delay higher thread
from accessing driver. It is enough that there are jobs with higher
prio than lowest prio tcp/ip sending thread, even if they have nothing
to do with network.

-- 
Nebojša
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-05-28 14:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 12:45 e1000e 82574L transmit latency? Stanislav Meduna
2013-05-28 13:01 ` Nebojša Ćosić
2013-05-28 13:49   ` Stanislav Meduna
2013-05-28 14:09     ` Nebojša Ćosić [this message]
2013-05-28 14:05   ` Stanislav Meduna
2013-05-28 14:15     ` Nebojša Ćosić

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=20130528160907.2d98fc65@sth491dt.servo.net \
    --to=nebojsa@asnn.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=stano@meduna.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox