linux-kernel - Re: [PATCH net-next RFC] net: increase LL_MAX

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20150917.131037.2286760949122849895.davem@davemloft.net>
Date:	Thu, 17 Sep 2015 13:10:37 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	kys@...rosoft.com
Cc:	David.Laight@...LAB.COM, alexander.duyck@...il.com,
	haiyangz@...rosoft.com, vkuznets@...hat.com,
	netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
	jasowang@...hat.com
Subject: Re: [PATCH net-next RFC] net: increase LL_MAX_HEADER for Hyper-V

From: KY Srinivasan <kys@...rosoft.com>
Date: Thu, 17 Sep 2015 19:52:01 +0000

> 
> 
>> -----Original Message-----
>> Have a pre-cooked ring of buffers for these descriptors that you can
>> point the chip at.  No per-packet allocation is necessary at all.
> 
> Even if I had a ring of buffers, I would still need to manage the life cycle
> of these buffers - selecting an unused one on the transmit path and marking
> it used (atomically).

Have one per TX ring entry, then the lifetime matches the lifetime of the
TX entry itself and therefore you need do nothing.

That's the whole idea.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/