From: "Nebojša Ćosić" <nebojsa@asnn.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: eg Engleder Gerhard <eg@keba.com>,
linux-rt-users <linux-rt-users@vger.kernel.org>
Subject: Re: UDP jitter
Date: Sat, 9 Nov 2013 11:26:12 +0100 [thread overview]
Message-ID: <20131109112612.4b45942e@sanja.asnn.org> (raw)
In-Reply-To: <alpine.DEB.2.02.1311081432300.23353@ionos.tec.linutronix.de>
Дана Fri, 8 Nov 2013 14:35:44 +0100 (CET)
Thomas Gleixner <tglx@linutronix.de> написа:
> On Fri, 8 Nov 2013, eg Engleder Gerhard wrote:
> > > -----Ursprüngliche Nachricht-----
> > > Von: Thomas Gleixner [mailto:tglx@linutronix.de]
> > > Gesendet: Freitag, 08. November 2013 12:31
> > > An: Stanislav Meduna
> > > Cc: Nebojša Ćosić; eg Engleder Gerhard; linux-rt-users
> > > Betreff: Re: UDP jitter
> > >
> > > There are other ways to solve this without touching a single
> > > line of kernel code. The technology is all there, you just
> > > have to use it. Of course that requires to understand it in
> > > the first place, though this seems to be way harder than
> > > spending a lot of time tracing the problem and then yelling
> > > "priority inversion" and hope that the RT folks are going to "fix" it.
> >
> > Can you give us a hint which technology to use? Currently I am
> > trying to use QoS Multi Band Priority Queueing.
>
> Well, it really depends on your requirements. Assuming you have a
> simple binary decision (Bulk and VIP traffic) a simple 2 band priority
> queue should work.
And how exactly is it going to help? You still have fifo, and you still
get messages from higher priority thread stuck waiting for low priority
task to finish sending whatever it has in there (please note how I
avoid mentioning priority inversion here).
By the way, by default you have pfifo_fast in there, which is capable
enough to do the priority based queuing.
>
> Thanks,
>
> tglx
Excuse my ignorance
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
next prev parent reply other threads:[~2013-11-09 10:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-29 20:22 UDP jitter Nebojša Ćosić
2013-04-30 15:22 ` Carsten Emde
2013-04-30 17:26 ` Nebojša Ćosić
2013-11-06 8:53 ` AW: " eg Engleder Gerhard
2013-11-06 11:57 ` Nebojša Ćosić
2013-11-06 19:07 ` Thomas Gleixner
2013-11-07 8:00 ` AW: " eg Engleder Gerhard
2013-11-07 9:33 ` Nebojša Ćosić
2013-11-08 2:07 ` Thomas Gleixner
2013-11-08 9:39 ` Stanislav Meduna
2013-11-08 10:32 ` Nebojša Ćosić
2013-11-08 11:48 ` Thomas Gleixner
2013-11-08 12:22 ` Armin Steinhoff
2013-11-08 18:57 ` E-Blokos
2013-11-08 10:50 ` Tom Cook
2013-11-08 10:51 ` AW: " eg Engleder Gerhard
2013-11-08 11:30 ` Thomas Gleixner
2013-11-08 12:07 ` AW: " eg Engleder Gerhard
2013-11-08 13:35 ` Thomas Gleixner
2013-11-09 10:26 ` Nebojša Ćosić [this message]
2013-11-09 16:33 ` Joe Korty
2013-11-08 12:14 ` Stanislav Meduna
2013-11-08 13:32 ` Thomas Gleixner
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=20131109112612.4b45942e@sanja.asnn.org \
--to=nebojsa@asnn.org \
--cc=eg@keba.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).