linux-kernel - Re: [PATCH] drm/ttm: remove padding from ttm_ref

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: <4B644E11.5060002@vmware.com>
Date:	Sat, 30 Jan 2010 16:19:45 +0100
From:	Thomas Hellstrom <thellstrom@...are.com>
To:	Richard Kennedy <richard@....demon.co.uk>
CC:	David Airlie <airlied@...ux.ie>,
	lkml <linux-kernel@...r.kernel.org>,
	"dri-devel@...ts.sourceforge.net" <dri-devel@...ts.sourceforge.net>
Subject: Re: [PATCH] drm/ttm: remove padding from ttm_ref_object on 64bit
 builds

Richard Kennedy wrote:
> Re-order structure ttm_ref_object to remove 8 bytes of alignment padding
> on 64 bit builds, so shrinking its size from 72 to 64 bytes allowing it
> to fit into a smaller slab.
>
> Signed-off-by: Richard Kennedy <richard@....demon.co.uk>
> ----
> patch against 2.6.33-rc5
> compiled & tested on x86_64 AMDX2 and nouveau 
> regards
> Richard
>
>
> diff --git a/drivers/gpu/drm/ttm/ttm_object.c b/drivers/gpu/drm/ttm/ttm_object.c
> index 1099aba..75e9d6f 100644
> --- a/drivers/gpu/drm/ttm/ttm_object.c
> +++ b/drivers/gpu/drm/ttm/ttm_object.c
> @@ -109,8 +109,8 @@ struct ttm_ref_object {
>  	struct drm_hash_item hash;
>  	struct list_head head;
>  	struct kref kref;
> -	struct ttm_base_object *obj;
>  	enum ttm_ref_type ref_type;
> +	struct ttm_base_object *obj;
>  	struct ttm_object_file *tfile;
>  };
>  
>
>
>   
Acked-by: Thomas Hellstrom <thellstrom@...are.com>


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