From: Michael Buesch <mb@bu3sch.de>
To: linuxppc-dev@lists.ozlabs.org
Cc: Jonathan Haws <Jonathan.Haws@sdl.usu.edu>
Subject: Re: Network Stack SKB Reallocation
Date: Mon, 26 Oct 2009 20:13:50 +0100 [thread overview]
Message-ID: <200910262013.52458.mb@bu3sch.de> (raw)
In-Reply-To: <BB99A6BA28709744BF22A68E6D7EB51F0330BEB38D@midas.usurf.usu.edu>
On Monday 26 October 2009 19:43:00 Jonathan Haws wrote:
> Quick question about the network stack in general:
>
> Does the stack itself release an SKB allocated by the device driver back to the heap upstream, or does it require that the device driver handle that?
There's the concept of passing responsibilities for the frames between
the networking layers. So the driver passes the frame and all responsibilities
to the networking stack. So if the networking stack accepts the packet in the first place,
it needs to free it (or pass it to somebody else to take care of).
--
Greetings, Michael.
next prev parent reply other threads:[~2009-10-26 19:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-26 18:43 Network Stack SKB Reallocation Jonathan Haws
2009-10-26 19:13 ` Michael Buesch [this message]
2009-10-26 19:16 ` Jonathan Haws
2009-10-27 13:43 ` john.p.price
2009-10-27 14:28 ` Jonathan Haws
2009-10-27 15:33 ` john.p.price
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=200910262013.52458.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Jonathan.Haws@sdl.usu.edu \
--cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.