From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] QoS on receive
Date: Sat, 16 Jul 2005 12:04:57 +0000 [thread overview]
Message-ID: <42D8F7E9.5010408@dsl.pipex.com> (raw)
In-Reply-To: <42D6898C.4050502@ti.com>
Alexander Sirotkin wrote:
> It appears that while Linux has plenty of traffic shaping mechanism on
> transmit, there is nothing on receive side.
> While generally it does make sense since transmit is more CPU intensive
> operation, after all receive also
> consumes CPU cycles. It is clear that it's best to drop the packet as
> soon as possible, i.e. on receive, if possible -
> by the driver itself. It may not be feasible in general case, but I can
> think of a couple of scenarios when it does
> make sense.
>
> Any ideas ?
> Maybe there is some similar QoS mechanism that I'm not aware of ?
>
Yes it's called ingress policing there is mention in LARTC and it is
possible to do quite complicated things with it. See the diffserv
examples in iproute2.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-07-16 12:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-14 15:49 [LARTC] QoS on receive Alexander Sirotkin
2005-07-15 3:41 ` pramod
2005-07-16 12:04 ` Andy Furniss [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=42D8F7E9.5010408@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=lartc@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 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.