public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ravikiran G Thirumalai <kiran@in.ibm.com>
To: linux-kernel@vger.kernel.org
Subject: Question regarding Qdisc.stats
Date: Tue, 20 Aug 2002 17:14:31 +0530	[thread overview]
Message-ID: <20020820171431.K1992@in.ibm.com> (raw)

Where do the Qdisc.stats show up? in /proc? (Assuming CONFIG_NET_SCHED is
not defined) I can see that it is copied to the skb from 
qdisc_copy_stats with 'TCA_STATS' attribute, but where is it being 
reported? or what is it being used for ?? Specifically, does 
Qdisc.stats.drops get reported anywere?

While I am at it, I see that qdisc->enqueue routines kfree the skb with the
dev->queue_lock held (when the enqueue routine drops the packet -- 
NET_XMIT_DROP)  from dev_queue_xmit. kfree_skb can be done outside the 
lock.... right? I can make a patch for this if I am not missing something.....

TIA
Kiran

             reply	other threads:[~2002-08-20 11:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-20 11:44 Ravikiran G Thirumalai [this message]
2002-09-15  5:46 ` Question regarding Qdisc.stats Werner Almesberger

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=20020820171431.K1992@in.ibm.com \
    --to=kiran@in.ibm.com \
    --cc=linux-kernel@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