From: Eric Dumazet <eric.dumazet@gmail.com>
To: YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
Cc: David Miller <davem@davemloft.net>, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH net-next] ndisc: Remove unused space at tail of skb for ndisc messages. (TAKE 3)
Date: Fri, 04 Jan 2013 08:00:19 -0800 [thread overview]
Message-ID: <1357315219.1678.1461.camel@edumazet-glaptop> (raw)
In-Reply-To: <50E6DFEC.7080603@linux-ipv6.org>
On Fri, 2013-01-04 at 22:58 +0900, YOSHIFUJI Hideaki wrote:
> Currently, the size of skb allocated for NDISC is MAX_HEADER +
> LL_RESERVED_SPACE(dev) + packet length + dev->needed_tailroom,
> but only LL_RESERVED_SPACE(dev) bytes is "reserved" for headers.
> As a result, the skb looks like this (after construction of the
> message):
>
> head data tail end
> +--------------------------------------------------------------+
> + | | | |
> +--------------------------------------------------------------+
> |<-hlen---->|<---ipv6 packet------>|<--tlen-->|<--MAX_HEADER-->|
> =LL_ = dev
> RESERVED_ ->needed_
> SPACE(dev) tailroom
>
> As the name implies, "MAX_HEADER" is used for headers, and should
> be "reserved" in prior to packet construction. Or, if some space
> is really required at the tail of ther skb, it should be
> explicitly documented.
>
> We have several option after construction of NDISC message:
>
> Option 1:
>
> head data tail end
> +---------------------------------------------+
> + | | |
> +---------------------------------------------+
> |<-hlen---->|<---ipv6 packet------>|<--tlen-->|
> =LL_ = dev
> RESERVED_ ->needed_
> SPACE(dev) tailroom
Acked-by: Eric Dumazet <edumazet@google.com>
Thanks !
next prev parent reply other threads:[~2013-01-04 16:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-04 13:58 [PATCH net-next] ndisc: Remove unused space at tail of skb for ndisc messages. (TAKE 3) YOSHIFUJI Hideaki
2013-01-04 16:00 ` Eric Dumazet [this message]
2013-01-04 23:17 ` David Miller
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=1357315219.1678.1461.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=yoshfuji@linux-ipv6.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