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: <20100227.014618.193735140.davem@davemloft.net>
Date:	Sat, 27 Feb 2010 01:46:18 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	shemminger@...tta.com
Cc:	dm@...lsio.com, netdev@...r.kernel.org
Subject: Re: [PATCH 4/7] cxgb4: Add packet queues and packet DMA code

From: Stephen Hemminger <shemminger@...tta.com>
Date: Fri, 26 Feb 2010 15:57:56 -0800

> On Fri, 26 Feb 2010 15:35:36 -0800
> Dimitris Michailidis <dm@...lsio.com> wrote:
> 
>> +
>> +/**
>> + *	need_skb_unmap - does the platform need unmapping of sk_buffs?
>> + *
>> + *	Returns true if the platfrom needs sk_buff unmapping.  The compiler
>> + *	optimizes away unecessary code if this returns true.
>> + */
>> +static inline int need_skb_unmap(void)
>> +{
>> +	/*
>> +	 * This structure is used to tell if the platfrom needs buffer
>> +	 * unmapping by checking if DECLARE_PCI_UNMAP_ADDR defines anything.
>> +	 */
>> +	struct dummy {
>> +		DECLARE_PCI_UNMAP_ADDR(addr);
>> +	};
>> +
>> +	return sizeof(struct dummy) != 0;
>> +}
>> +
> 
> I would prefer one code path and let the compiler decide if unmap
> should be nop; rather than this kind of trick code.

Agreed, this is rediculious.  And there is currently no platform that
matters where this will trigger.

With IOMMUs and even the swiommu layer, even bog standard x86 systems
need the unmap addresses.

Therefore optimizing this is totally unreasonable.  Just use the provided
APIs and let the compiler and the platform defines do the work.

I'm amazed at how people do stuff like this.  If it's a reasonable
opimization, maybe, JUST MAYBE, it's better to optimize it generically
so that every driver gets the benefit NOT JUST YOUR individual driver.

--
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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ