From: Grant Edwards <grant.b.edwards@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: Change in alloc_skb() behavior in 3.2+ kernels?
Date: Wed, 6 Jun 2012 20:24:00 +0000 (UTC) [thread overview]
Message-ID: <jqoe90$fs3$2@dough.gmane.org> (raw)
In-Reply-To: 20120606.131703.870120997635192180.davem@davemloft.net
On 2012-06-06, David Miller <davem@davemloft.net> wrote:
> From: Grant Edwards <grant.b.edwards@gmail.com>
> Date: Wed, 6 Jun 2012 19:01:40 +0000 (UTC)
>
>> That's what I'll do as soon as I can find a definition of what the API
>> for alloc_skb() actually _is_. It has clearly changed in the past few
>> years.
>
> And it will continue to change. There are no stable APIs inside of
> the kernel, none.
Oh, I know (as does anybody who has maintained a driver for more than
a few months). Right now, I'm just trying to find out what the
current API for alloc_skb() is.
Is skb_tailroom() guaranteed to be >= the requested size?
--
Grant Edwards grant.b.edwards Yow! I'm wet! I'm wild!
at
gmail.com
next prev parent reply other threads:[~2012-06-06 20:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 18:32 Change in alloc_skb() behavior in 3.2+ kernels? Grant Edwards
2012-06-06 18:42 ` Eric Dumazet
2012-06-06 18:59 ` Grant Edwards
2012-06-06 19:02 ` David Miller
2012-06-06 20:22 ` Grant Edwards
2012-06-07 1:23 ` [PATCH net-next] net: Update kernel-doc for __alloc_skb() Ben Hutchings
2012-06-07 20:19 ` David Miller
2012-06-07 13:23 ` Change in alloc_skb() behavior in 3.2+ kernels? Grant Edwards
2012-06-07 14:01 ` Eric Dumazet
2012-06-07 14:16 ` Grant Edwards
2012-06-07 14:25 ` Eric Dumazet
2012-06-06 18:51 ` David Miller
2012-06-06 19:01 ` Grant Edwards
2012-06-06 20:17 ` David Miller
2012-06-06 20:24 ` Grant Edwards [this message]
2012-06-06 20:31 ` Eric Dumazet
2012-06-06 20:35 ` Grant Edwards
2012-06-06 19:42 ` Eric Dumazet
2012-06-06 20:26 ` Grant Edwards
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='jqoe90$fs3$2@dough.gmane.org' \
--to=grant.b.edwards@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).