From: Chetan Kumar <shivakumar.chetan@gmail.com>
To: Asim Shankar <asimshankar@gmail.com>
Cc: netdev@oss.sgi.com
Subject: Re: Some query on ingress policing
Date: Fri, 18 Feb 2005 12:49:43 +0530 [thread overview]
Message-ID: <17fe83cb050217231925c43a8e@mail.gmail.com> (raw)
In-Reply-To: <7bca1cb5050217150642addd71@mail.gmail.com>
Yes, That is the point. Now since the ingress policing is done in
net_rx_action (i.e) after queueing the packet on the input queue, the
packet which was misbehaving would have used the queue resources. One
would drop the packet only after you clear the backlog queue, and a
greedy flow could potentially over-run the buffer of well behaved
flows.
Also another serious issues is that if I ever want to provide priority
for the VOIP traffic, that is not feasible since the backlog queue is
drained in a FIFO manner.
On Thu, 17 Feb 2005 17:06:13 -0600, Asim Shankar <asimshankar@gmail.com> wrote:
> > I was going thro the packet journey thro the network stack in Linux.
> > Now if I want enable ingress policing, it looks like packet
> > classification and policing should happen in netif_rx (i.e in the
> > interrupt context) before packet is queued on to the input queue am I
> > missing something.
>
> My understanding is that ingress policing (the
> qdisc_ingress->enqueue() call) is done in the softint. See
> netif_receive_skb() for a call to ing_filter().
>
> Alternatively, if CONFIG_NET_CLS_ACT=n and CONFIG_NETFILTER=y then the
> policing happens as an NF_IP_PRE_ROUTING netfilter hook instead.
>
> Also, netif_rx() is not the single point of entry for skb's to the
> stack. NAPI drivers are polled for packets, so packets aren't always
> picked up from the NIC in the interrupt context.
>
> Hope that helps,
>
> -- Asim
>
prev parent reply other threads:[~2005-02-18 7:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17fe83cb0502160349a4190d1@mail.gmail.com>
2005-02-17 0:32 ` Some query on ingress policing Chetan Kumar
[not found] ` <7bca1cb5050217150642addd71@mail.gmail.com>
2005-02-18 7:19 ` Chetan Kumar [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=17fe83cb050217231925c43a8e@mail.gmail.com \
--to=shivakumar.chetan@gmail.com \
--cc=asimshankar@gmail.com \
--cc=netdev@oss.sgi.com \
/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).