From: Stephen Hemminger <stephen@networkplumber.org>
To: Arun Kumar Neelakantam <aneela@codeaurora.org>
Cc: netdev@vger.kernel.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
Chris Lew <clew@codeaurora.org>
Subject: Re: netdev_alloc_skb is failing for 16k length
Date: Mon, 27 May 2019 07:59:56 -0700 [thread overview]
Message-ID: <20190527075956.26f869ec@hermes.lan> (raw)
In-Reply-To: <6891cd8b-a3be-91f5-39c4-7a7e7d498921@codeaurora.org>
On Mon, 27 May 2019 12:21:51 +0530
Arun Kumar Neelakantam <aneela@codeaurora.org> wrote:
> Hi team,
>
> we are using "skb = netdev_alloc_skb(NULL, len);" which is getting
> failed sometimes for len = 16k.
>
> I suspect mostly system memory got fragmented and hence atomic memory
> allocation for 16k is failing, can you please suggest best way to handle
> this failure case.
>
> Thanks
>
> Arun N
>
If you are handling big frames, then put the data in page size chunks
and use build_skb.
next prev parent reply other threads:[~2019-05-27 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 6:51 netdev_alloc_skb is failing for 16k length Arun Kumar Neelakantam
2019-05-27 14:59 ` Stephen Hemminger [this message]
2019-05-28 10:08 ` Arun Kumar Neelakantam
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=20190527075956.26f869ec@hermes.lan \
--to=stephen@networkplumber.org \
--cc=aneela@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=clew@codeaurora.org \
--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).