From: Ben Collins <bcollins@debian.org>
To: Sushant Sharma <sushant@cs.unm.edu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: when is alloc_skb called
Date: Mon, 7 Jun 2004 18:57:44 -0400 [thread overview]
Message-ID: <20040607225744.GA26253@phunnypharm.org> (raw)
In-Reply-To: <40C4DE2A.1070008@cs.unm.edu>
On Mon, Jun 07, 2004 at 03:29:14PM -0600, Sushant Sharma wrote:
> Hi All
>
> I want to know which are the evnets
> that can lead to the calling of alloc_skb
> function which is used to allocate sk_buff.
> Arrival and departure of packet are 2 events
> which I know. Are there any other events/cases
> which can lead to alloc_skb(...) function call in kernel.
Some non-network related drivers use skb's for non-network related
things (ieee1394 is one such abuser).
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/
next prev parent reply other threads:[~2004-06-07 23:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-07 21:29 Sushant Sharma
2004-06-07 22:57 ` Ben Collins [this message]
2004-06-26 5:16 ` Arnaldo Carvalho de Melo
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=20040607225744.GA26253@phunnypharm.org \
--to=bcollins@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sushant@cs.unm.edu \
/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
all inboxes | Powered by JetHome®