mesa/src/gallium
Ilia Mirkin bacf8471dc nouveau: set texture upload budget
It doesn't seem like the exact number has too much effect on the
performaince in "teximage". However setting it to just about anything
prevents some OOMs from getting hit. These values are not well-tuned,
but don't seem too bad.

Signed-off-by: Ilia Mirkin <imirkin@alum.mit.edu>
2018-12-03 23:11:29 -05:00
..
auxiliary draw: fix infinite loop in line stippling 2018-11-29 18:39:40 +01:00
docs gallium: New cap PIPE_CAP_MAX_VERTEX_ELEMENT_SRC_OFFSET. 2018-09-10 07:59:31 +02:00
drivers nouveau: set texture upload budget 2018-12-03 23:11:29 -05:00
include winsys/amdgpu: explicitly declare whether buffer_map is permanent or not 2018-11-28 18:24:14 +01:00
state_trackers st/xvmc: Add X11 include path. 2018-11-30 22:09:43 -08:00
targets d3dadapter9: use snprintf(..., "%s", ...) instead of strncpy 2018-12-01 21:32:53 +01:00
tests gallium: Fix uninitialized variable warning in compute test. 2018-11-27 11:23:22 -08:00
tools trace: Fix parsing of recent traces. 2018-06-04 21:06:31 +01:00
winsys Revert "winsys/amdgpu: overallocate buffers for faster address translation on Gfx9" 2018-11-29 14:46:06 -05:00
Android.common.mk Android: rework LLVM build support 2017-05-11 13:52:21 +01:00
Android.mk android: Build kms_swrast for the Android platform 2018-10-22 13:08:17 +01:00
Automake.inc gallium: Fix automake for Android (v2) 2018-06-27 19:58:16 -07:00
Makefile.am v3d: Rename the driver files from "vc5" to "v3d". 2018-05-16 21:19:07 +01:00
meson.build v3d: Rename the driver files from "vc5" to "v3d". 2018-05-16 21:19:07 +01:00
README.portability
SConscript gallium: move ddebug, noop, rbug, trace to auxiliary to improve build times 2018-04-13 14:08:14 -04:00

	      CROSS-PLATFORM PORTABILITY GUIDELINES FOR GALLIUM3D 


= General Considerations =

The state tracker and winsys driver support a rather limited number of
platforms. However, the pipe drivers are meant to run in a wide number of
platforms. Hence the pipe drivers, the auxiliary modules, and all public
headers in general, should strictly follow these guidelines to ensure


= Compiler Support =

* Include the p_compiler.h.

* Cast explicitly when converting to integer types of smaller sizes.

* Cast explicitly when converting between float, double and integral types.

* Don't use named struct initializers.

* Don't use variable number of macro arguments. Use static inline functions
instead.

* Don't use C99 features.

= Standard Library =

* Avoid including standard library headers. Most standard library functions are
not available in Windows Kernel Mode. Use the appropriate p_*.h include.

== Memory Allocation ==

* Use MALLOC, CALLOC, FREE instead of the malloc, calloc, free functions.

* Use align_pointer() function defined in u_memory.h for aligning pointers
 in a portable way.

== Debugging ==

* Use the functions/macros in p_debug.h.

* Don't include assert.h, call abort, printf, etc.


= Code Style =

== Inherantice in C ==

The main thing we do is mimic inheritance by structure containment.

Here's a silly made-up example:

/* base class */
struct buffer
{
  int size;
  void (*validate)(struct buffer *buf);
};

/* sub-class of bufffer */
struct texture_buffer
{
  struct buffer base;  /* the base class, MUST COME FIRST! */
  int format;
  int width, height;
};


Then, we'll typically have cast-wrapper functions to convert base-class 
pointers to sub-class pointers where needed:

static inline struct vertex_buffer *vertex_buffer(struct buffer *buf)
{
  return (struct vertex_buffer *) buf;
}


To create/init a sub-classed object:

struct buffer *create_texture_buffer(int w, int h, int format)
{
  struct texture_buffer *t = malloc(sizeof(*t));
  t->format = format;
  t->width = w;
  t->height = h;
  t->base.size = w * h;
  t->base.validate = tex_validate;
  return &t->base;
}

Example sub-class method:

void tex_validate(struct buffer *buf)
{
  struct texture_buffer *tb = texture_buffer(buf);
  assert(tb->format);
  assert(tb->width);
  assert(tb->height);
}


Note that we typically do not use typedefs to make "class names"; we use
'struct whatever' everywhere.

Gallium's pipe_context and the subclassed psb_context, etc are prime examples 
of this.  There's also many examples in Mesa and the Mesa state tracker.