From: Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>
To: Alexander Smirnov <alex.bluesman.smirnov@gmail.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
davem@davemloft.net, slapin@ossfans.org,
linux-zigbee-devel@lists.sourceforge.net, netdev@vger.kernel.org,
jonsmirl@gmail.com
Subject: Re: [IEEE802.15.4][6LoWPAN] draft for fragmentation support
Date: Thu, 20 Oct 2011 17:13:27 +0400 [thread overview]
Message-ID: <4EA01E77.8040300@gmail.com> (raw)
In-Reply-To: <CAJmB2rCe3BJKD07TOSyAT0vbDq_K1VHLOtECqeOMzaTsg3DokA@mail.gmail.com>
Hi, Alexander, colleagues,
On 10/20/2011 04:50 PM, Alexander Smirnov wrote:
> Hi Eric,
>
> thank you for the replies. And another question I forgot to ask:
>
> when I send fragments, I still have original skb buffer. What should I
> do with it, is there any
> "proper/good" ways to drop it? Because I've already fragmented it and
> do not need to send
> original skb to queue.
You might want to check the TCP/IP fragmentation code path. I think you
can drop it with kfree_skb, but I ain't sure ATM.
>
> Thank you,
> Alexander
P.S. Top posting is really a bad style. And it's now that welcome in the
MLs.
--
With best wishes
Dmitry
next prev parent reply other threads:[~2011-10-20 13:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 11:17 [IEEE802.15.4][6LoWPAN] draft for fragmentation support Alexander Smirnov
2011-10-20 11:17 ` Alexander Smirnov
2011-10-20 11:22 ` walter harms
2011-10-20 12:39 ` Eric Dumazet
2011-10-20 12:50 ` Alexander Smirnov
2011-10-20 13:11 ` Eric Dumazet
2011-10-20 13:13 ` Dmitry Eremin-Solenikov [this message]
2011-10-20 13:51 ` Eric Dumazet
[not found] ` <20111020111718.GA32181-AUGNqIMGY+aR2kOLt6zJ8ErlnG4Plg33XqFh9Ls21Oc@public.gmane.org>
2011-10-20 13:54 ` Dmitry Eremin-Solenikov
2011-10-20 13:54 ` Dmitry Eremin-Solenikov
[not found] ` <4EA02818.9000206-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-10-20 15:11 ` Alexander Smirnov
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=4EA01E77.8040300@gmail.com \
--to=dbaryshkov@gmail.com \
--cc=alex.bluesman.smirnov@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jonsmirl@gmail.com \
--cc=linux-zigbee-devel@lists.sourceforge.net \
--cc=netdev@vger.kernel.org \
--cc=slapin@ossfans.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.