netdev - Re: Network device with variable hard header len

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

Date:	Mon, 12 Jan 2009 11:48:19 +0000
From:	Mark Brown <broonie@...ena.org.uk>
To:	Dmitry Eremin-Solenikov <dbaryshkov@...il.com>
Cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: Network device with variable hard header len

On Sat, Jan 10, 2009 at 02:28:12PM +0300, Dmitry Eremin-Solenikov wrote:

> Sorry if this a dumb question. Currently I'm programming a driver for
> the devices with variable network header len. From the Linux net stack
> perspective what should I do: set netdev->hard_header_len to maximum
> possible header and use less space that specified there or set
> netdev->needed_headroom to that value?

> If that metters, I'll be implementing my own set of header_ops in any
> case.

This is probably better asked on netdev (CCed).
--
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