From: "David S. Miller" <davem@redhat.com>
To: haveblue@us.ibm.com
Cc: manand@us.ibm.com, bcrl@redhat.com, alan@lxorguk.ukuu.org.uk,
bhartner@us.ibm.com, linux-kernel@vger.kernel.org,
lse-tech@lists.sourceforge.net,
lse-tech-admin@lists.sourceforge.net
Subject: Re: [Lse-tech] Re: (RFC): SKB Initialization
Date: Fri, 23 Aug 2002 15:41:14 -0700 (PDT) [thread overview]
Message-ID: <20020823.154114.99162408.davem@redhat.com> (raw)
In-Reply-To: <3D666531.4020909@us.ibm.com>
From: Dave Hansen <haveblue@us.ibm.com>
Date: Fri, 23 Aug 2002 09:39:13 -0700
Where are interrupts disabled? I just went through a set of kernprof
data and traced up the call graph. In the most common __kfree_skb
case, I do not believe that it has interupts disabled. I could be
wrong, but I didn't see it.
That's completely right. interrupts should never be disabled when
__kfree_skb is executed. It used to be possible when we allowed
it to be invoked from interrupt handlers, but that is illegal and
we have kfree_skb_irq which just reschedules the actual __kfree_skb
to a software interrupt.
So I agree with you, Mala's claims seem totally bogus and not well
founded at all.
next prev parent reply other threads:[~2002-08-23 22:52 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-23 14:44 [Lse-tech] Re: (RFC): SKB Initialization Mala Anand
2002-08-23 16:39 ` Dave Hansen
2002-08-23 20:12 ` Bill Hartner
2002-08-23 20:30 ` Dave Hansen
2002-08-23 23:36 ` Troy Wilson
2002-08-23 20:51 ` Rick Lindsley
2002-08-23 22:41 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-09-03 3:47 Mala Anand
2002-08-27 13:18 Mala Anand
2002-08-27 15:49 ` jamal
2002-08-27 2:53 Mala Anand
2002-08-26 13:04 Mala Anand
2002-08-26 19:28 ` Robert Olsson
2002-08-27 10:17 ` jamal
2002-08-25 20:12 Mala Anand
2002-08-26 1:02 ` jamal
2002-08-25 16:17 jamal
2002-08-25 22:51 ` David S. Miller
2002-08-23 23:38 Mala Anand
2002-08-23 23:55 ` David S. Miller
2002-08-23 23:14 Mala Anand
2002-08-22 17:22 Mala Anand
2002-08-22 18:32 ` Benjamin LaHaise
2002-08-22 19:02 ` Dave Hansen
2002-08-22 22:05 ` William Lee Irwin III
2002-08-23 19:09 ` Bill Hartner
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=20020823.154114.99162408.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@redhat.com \
--cc=bhartner@us.ibm.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lse-tech-admin@lists.sourceforge.net \
--cc=lse-tech@lists.sourceforge.net \
--cc=manand@us.ibm.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