netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Radha Mohan <radhamohan_ch@yahoo.com>
To: jon_zhou@agilent.com, netdev@vger.kernel.org
Subject: Re: can we reuse an skb
Date: Fri, 19 Jun 2009 12:40:08 +0530 (IST)	[thread overview]
Message-ID: <207157.90170.qm@web94803.mail.in2.yahoo.com> (raw)
In-Reply-To: <60230E21F17E384C9BF0B9C98D9E3FDC048963D6@sgp-sg-mb02.sgp.agilent.com>



We may need to modify the part in kernel where kfree_skb() will be called somewhere after copying to user space. Right?

I came to know that Windows NDIS has this type of facility. The NDIS gives back the buffer after copying to application.

I came across a patch made long ago for 2.4.19 citing the same concept
http://www.candelatech.com/oss/napi_tune_2.4.19.patch

-- Mohan



----- Original Message ----
From: "jon_zhou@agilent.com" <jon_zhou@agilent.com>
To: radhamohan_ch@yahoo.com; netdev@vger.kernel.org
Sent: Friday, 19 June, 2009 12:21:45 PM
Subject: RE: can we reuse an skb

I am also thinking about this...

i.e.pcnet32.c
seems the skb will be claimed to be unuseful(mark some bits) in the device driver, than it will be recycled in the softirq handler,

that means unable to reuse it, unless modidy the driver.

Regards,
zhou rui

-----Original Message-----
From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.org] On Behalf Of Radha Mohan
Sent: Friday, June 19, 2009 2:47 PM
To: netdev@vger.kernel.org
Subject: can we reuse an skb


Hi,

For an ethernet driver, we need to allocate some pool of SKBs for receiving packets. Is there any way we can reuse the same SKBs without the need to re-allocate in atomic every time one has been used up for netif_rx(). 

Any pointers will be helpful.

-- Mohan


      ICC World Twenty20 England '09 exclusively on YAHOO! CRICKET http://cricket.yahoo.com

--
To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@vger.kernel.org More majordomo info at  http://vger.kernel.org/majordomo-info.html


      ICC World Twenty20 England &#39;09 exclusively on YAHOO! CRICKET http://cricket.yahoo.com


  reply	other threads:[~2009-06-19  7:22 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-19  6:46 can we reuse an skb Radha Mohan
2009-06-19  6:51 ` jon_zhou
2009-06-19  7:10   ` Radha Mohan [this message]
2009-06-19  7:21   ` Peter Chacko
2009-06-19 10:37 ` Saikiran Madugula
2009-06-19 18:41   ` Neil Horman
2009-06-19 16:56 ` Rick Jones
2009-06-19 23:29   ` David Miller
2009-06-20  3:54     ` Peter Chacko
2009-06-20  8:00       ` Evgeniy Polyakov
2009-06-20 11:51       ` Ben Hutchings
2009-06-21  5:41     ` Peter Chacko
2009-06-21  5:49       ` David Miller
2009-06-21 11:46       ` [RFD] Pluggable code design (was: can we reuse an skb) Al Boldi
  -- strict thread matches above, loose matches on Subject: below --
2009-06-19 10:11 can we reuse an skb Nicholas Van Orton
2009-06-22 13:34 ` Philby John
2009-06-22 13:56   ` Peter Chacko
2009-06-22 14:33     ` Philby John

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=207157.90170.qm@web94803.mail.in2.yahoo.com \
    --to=radhamohan_ch@yahoo.com \
    --cc=jon_zhou@agilent.com \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).