All of lore.kernel.org
 help / color / mirror / Atom feed
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:35:50 +0000 (UTC)	[thread overview]
Message-ID: <jqoev6$l2b$1@dough.gmane.org> (raw)
In-Reply-To: 1339014685.26966.73.camel@edumazet-glaptop

On 2012-06-06, Eric Dumazet <eric.dumazet@gmail.com> wrote:
> On Wed, 2012-06-06 at 20:24 +0000, Grant Edwards wrote:
>
>> Is skb_tailroom() guaranteed to be >= the requested size?
>> 
>
> Of course, but only right after alloc_skb().

That's good enough.
     
-- 
Grant Edwards               grant.b.edwards        Yow! Okay ... I'm going
                                  at               home to write the "I HATE
                              gmail.com            RUBIK's CUBE HANDBOOK FOR
                                                   DEAD CAT LOVERS" ...

  reply	other threads:[~2012-06-06 20:36 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
2012-06-06 20:31         ` Eric Dumazet
2012-06-06 20:35           ` Grant Edwards [this message]
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='jqoev6$l2b$1@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.