netdev - Re: How to best consolidate list of skbs (msdu) for receive?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1393542195.26794.50.camel@edumazet-glaptop2.roam.corp.google.com>
Date:	Thu, 27 Feb 2014 15:03:15 -0800
From:	Eric Dumazet <eric.dumazet@...il.com>
To:	Ben Greear <greearb@...delatech.com>
Cc:	Florian Fainelli <f.fainelli@...il.com>,
	"linux-wireless@...r.kernel.org" <linux-wireless@...r.kernel.org>,
	netdev <netdev@...r.kernel.org>
Subject: Re: How to best consolidate list of skbs (msdu) for receive?

On Thu, 2014-02-27 at 14:38 -0800, Ben Greear wrote:

> Based on the code above, do you think skb_try_coalesce() is
> the best option for this logic?

Yep, if you do not know how are built the skb in the chain, I would say
using skb_try_coalesce() seems the proper way.

We use it for example in tcp input path.

Take also a look at tipc_link_recv_fragment()


--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html