From: Andi Kleen <andi@firstfloor.org>
To: Amit Uttamchandani <amit.uttam@gmail.com>
Cc: netdev <netdev@vger.kernel.org>
Subject: Re: Handling receive packets with limited buffer space
Date: Sat, 20 Mar 2010 16:01:40 +0100 [thread overview]
Message-ID: <8739zvca0b.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20100319094118.GA30249@debian> (Amit Uttamchandani's message of "Fri, 19 Mar 2010 02:41:18 -0700")
Amit Uttamchandani <amit.uttam@gmail.com> writes:
> In my modified ethoc.c driver, I am using only one receive buffer
> descriptor due to limited space. This works fairly well for small
> packets (arp, pings, etc.).
>
> However, doing a 'wget' and downloading a file causes lots of drops and
> thus results in a terminated connection.
>
> How do I go about dealing with this? I tried stopping the queue
> (netif_stop_queue) while I'm processing the rx skb and then resuming it
> once I'm done, but this did not seem to help.
>
> Any ideas on this?
You'll need to allocate a new skb and copy into it before
passing the data up the stack.
-Andi
--
ak@linux.intel.com -- Speaking for myself only.
prev parent reply other threads:[~2010-03-20 15:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 9:41 Handling receive packets with limited buffer space Amit Uttamchandani
2010-03-20 15:01 ` Andi Kleen [this message]
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=8739zvca0b.fsf@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=amit.uttam@gmail.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).