From: Stephen Hemminger <shemminger@linux-foundation.org>
To: vinay ravuri <vinaynyc@yahoo.com>
Cc: netdev@vger.kernel.org
Subject: Re: Socket Buffers and Memory Managment
Date: Thu, 19 Jul 2007 09:10:41 +0100 [thread overview]
Message-ID: <20070719091041.06f29789@oldman> (raw)
In-Reply-To: <261750.43078.qm@web82911.mail.mud.yahoo.com>
On Wed, 18 Jul 2007 23:51:03 -0700 (PDT)
vinay ravuri <vinaynyc@yahoo.com> wrote:
> How about the following approach:
>
> I allocate an skb of 0 bytes and replace data element
> of skb struct (i.e. skb.data = addr_given_by_hw) when
> the h/w interrupts me with a packet. I register for a
> destructor for this skb and when the kernel is ready
> to free the skb, I make sure that my free is invoked -
> Ofcourse this is assuming that their is a facility in
> linux socket buffers to be able to do destructors. Is
> this approach a viable, if so, are any gottcha's?
>
> -Vinay
You need to use frag list for that since upper layers expect to
be able to use that data area for normal use, ie bridging/routing, etc.
Also access to data area would be non-cached so you want to make
sure it is only accessed once.
But how will you handle a slow receiver where all the skb's end up
staying queued. Won't you exhaust your packet memory.
next prev parent reply other threads:[~2007-07-19 8:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-17 17:20 Socket Buffers and Memory Managment vinay ravuri
2007-07-17 19:41 ` Stephen Hemminger
2007-07-17 19:44 ` David Miller
2007-07-18 17:13 ` Roy Pledge
2007-07-18 21:22 ` Stephen Hemminger
2007-07-19 6:51 ` vinay ravuri
2007-07-19 7:04 ` pradeep singh
2007-07-19 8:10 ` Stephen Hemminger [this message]
2007-07-19 9:08 ` Evgeniy Polyakov
2007-07-20 11:50 ` Andi Kleen
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=20070719091041.06f29789@oldman \
--to=shemminger@linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=vinaynyc@yahoo.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).