From: "Ville Syrjälä" <syrjala@sci.fi>
To: Jerome Glisse <jglisse@redhat.com>
Cc: skeggsb@gmail.com, thellstrom@vmware.com, dri-devel@lists.sf.net
Subject: Re: [PATCH 1/4] drm/ttm: split no_wait argument in 2 GPU or reserve wait
Date: Thu, 25 Feb 2010 19:11:52 +0200 [thread overview]
Message-ID: <20100225171152.GP10145@sci.fi> (raw)
In-Reply-To: <1267116614-17393-2-git-send-email-jglisse@redhat.com>
On Thu, Feb 25, 2010 at 05:50:11PM +0100, Jerome Glisse wrote:
> There is case where we want to be able to wait only for the
> GPU while not waiting for other buffer to be unreserved. This
> patch split the no_wait argument all the way down in the whole
> ttm path so that upper level can decide on what to wait on or
> not.
>
> This patch break the API to other modules, update to others
> driver are following in separate patches.
>
> Signed-off-by: Jerome Glisse <jglisse@redhat.com>
> ---
> drivers/gpu/drm/ttm/ttm_bo.c | 57 ++++++++++++++++++++----------------
> drivers/gpu/drm/ttm/ttm_bo_util.c | 9 ++++--
> include/drm/ttm/ttm_bo_api.h | 6 ++-
> include/drm/ttm/ttm_bo_driver.h | 29 +++++++++++-------
> 4 files changed, 60 insertions(+), 41 deletions(-)
>
> diff --git a/drivers/gpu/drm/ttm/ttm_bo.c b/drivers/gpu/drm/ttm/ttm_bo.c
> index c7320ce..d2b2482 100644
> --- a/drivers/gpu/drm/ttm/ttm_bo.c
> +++ b/drivers/gpu/drm/ttm/ttm_bo.c
> @@ -357,7 +357,8 @@ static int ttm_bo_add_ttm(struct ttm_buffer_object *bo, bool zero_alloc)
>
> static int ttm_bo_handle_move_mem(struct ttm_buffer_object *bo,
> struct ttm_mem_reg *mem,
> - bool evict, bool interruptible, bool no_wait)
> + bool evict, bool interruptible,
> + bool no_wait_reserve, bool no_wait_gpu)
Code which calls these boolean monsters is very hard to read. How
about converting all of these booleans into some kind of flags?
--
Ville Syrjälä
syrjala@sci.fi
http://www.sci.fi/~syrjala/
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
--
next prev parent reply other threads:[~2010-02-25 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 16:50 TTM split no_wait argument in 2 (no_wait_reserve, no_wait_gpu) Jerome Glisse
2010-02-25 16:50 ` [PATCH 1/4] drm/ttm: split no_wait argument in 2 GPU or reserve wait Jerome Glisse
2010-02-25 16:50 ` [PATCH 2/4] drm/radeon/kms: update to TTM no_wait splitted argument Jerome Glisse
2010-02-25 16:50 ` [PATCH 3/4] drm/nouveau: " Jerome Glisse
2010-02-25 16:50 ` [PATCH 4/4] drm/vmwgfx: " Jerome Glisse
2010-02-25 17:11 ` Ville Syrjälä [this message]
2010-03-17 10:19 ` [PATCH 1/4] drm/ttm: split no_wait argument in 2 GPU or reserve wait Thomas Hellstrom
2010-03-04 10:12 ` TTM split no_wait argument in 2 (no_wait_reserve, no_wait_gpu) Jerome Glisse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100225171152.GP10145@sci.fi \
--to=syrjala@sci.fi \
--cc=dri-devel@lists.sf.net \
--cc=jglisse@redhat.com \
--cc=skeggsb@gmail.com \
--cc=thellstrom@vmware.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.