netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: netdev@vger.kernel.org
Subject: ingress policying for realtime protocol
Date: Tue, 19 May 2015 23:11:45 +0200	[thread overview]
Message-ID: <20150519211145.GA23134@pengutronix.de> (raw)

Hello,

I hope this is the/a right list to ask this question. If not, I'd be
happy to learn the right alternative.

For a system that implements the Media Redundancy Protocol (MRP,
http://en.wikipedia.org/wiki/Media_Redundancy_Protocol) I'm faced with
the task to assert that the corresponding ethernet packets are handled
"in time". Currently this fails already if I do

	scp somebigfile mymrpsystem:

The first idea was to use ingress policying to limit all packets that
are not related to MRP to a certain rate.

The problem in practise however is that the rate that has to be used
above is very low (100kbit) so we're looking for alternatives. I wonder
what's missing to get ingress policying more versatile to allow for
example a prio qdisc or if there is some conceptual problem that I don't
see. I'm not sure this would solve our problem, but it's definitely
something I want to play with before trying/resorting to hackish
solutions (like hacking the eth-driver to pipe MRP packets directly to
the network userspace application instead of through the network stack).

Do you have any ideas or hints?

Thanks in advance
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-König            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

             reply	other threads:[~2015-05-19 21:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19 21:11 Uwe Kleine-König [this message]
2015-05-20 23:46 ` ingress policying for realtime protocol Cong Wang
2015-05-21  0:30   ` Eric Dumazet
2015-05-21  1:47     ` Cong Wang
2015-05-21  1:53       ` Eric Dumazet
2015-05-21  1:59         ` Cong Wang
2015-05-21  2:32           ` Eric Dumazet
2015-05-21  7:07     ` Uwe Kleine-König
2015-05-21 13:36       ` Jamal Hadi Salim
2015-05-21 18:58         ` Uwe Kleine-König
2015-05-22 14:00           ` Jamal Hadi Salim
2015-05-21 14:04       ` Eric Dumazet

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=20150519211145.GA23134@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.de \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).