Skip to contentSkip to conversation

QoS on receive

LARTC Alexander Sirotkin 3 participants 3 messages Jul 14, 2005 – Jul 16, 2005

lore
Share & tools
lore
#0 lore raw

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 ?

Signature · 14 lines
Alexander Sirotkin
SW Engineer

Texas Instruments
Broadband Communications Israel (BCIL)
Tel:  +972-9-9706587
________________________________________________________________________
"Those who do not understand Unix are condemned to reinvent it, poorly."
      -- Henry Spencer 

_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
#1 lore raw

Dropping of packets on the receive side can be done bu IPTABLES..

thanks
pramod

Quoted 10 lines · Alexander Sirotkin

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.

Quoted 3 lines

Any ideas ?
Maybe there is some similar QoS mechanism that I'm not aware of ?

_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

#2 lore raw
In reply to Alexander Sirotkin
Quoted 10 lines · Alexander Sirotkin

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.

Quoted 3 lines

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
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc