Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Valerio Camassa <valerio993@gmail.com>
To: Robert Hooker <sarvatt@ubuntu.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: 3d performance very low
Date: Sun, 01 Aug 2010 17:33:28 +0200	[thread overview]
Message-ID: <4C5593C8.8080607@gmail.com> (raw)
In-Reply-To: <AANLkTikME-giyOWkRfLknZt6tpbhy1HAATOcXbmphDVs@mail.gmail.com>

  I tried to change .drirc to add the xml for dri2 but glxgears still 
rating ~60FPS. Also with "$ vblank_mode=0 glxgears" it rates ~60FPS.

Il 01/08/2010 17:26, Robert Hooker ha scritto:
> On Sat, Jul 31, 2010 at 4:36 AM, Valerio Camassa<valerio993@gmail.com>  wrote:
>>   I tried to change vblank_mode with driconf and with set param vblank_mode,
>> but i obtain the same fps with 2.11 and 2.12 drivers:
>>> 311 frames in 5.0 seconds = 62.175 FPS
>> With 2.12 glxgears rates ~700FPS.
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>>
> You need to add a seperate dri2 device to .drirc for vblank_mode to
> work there, driconf doesn't work right
>
>
>      <device screen="0" driver="dri2">
>          <application name="Default">
>              <option name="vblank_mode" value="0" />
>          </application>
>      </device>
>
> my full ~/.drirc for example
>
>
> <driconf>
>      <device screen="0" driver="dri2">
>          <application name="Default">
>              <option name="vblank_mode" value="0" />
>          </application>
>      </device>
>      <device screen="0" driver="i915">
>          <application name="Default">
>              <option name="force_s3tc_enable" value="false" />
>              <option name="no_rast" value="false" />
>              <option name="always_flush_cache" value="false" />
>              <option name="stub_occlusion_query" value="false" />
>              <option name="always_flush_batch" value="false" />
>              <option name="bo_reuse" value="1" />
>              <option name="texture_tiling" value="true" />
>              <option name="early_z" value="false" />
>              <option name="allow_large_textures" value="2" />
>              <option name="fragment_shader" value="false" />
>          </application>
>      </device>
> </driconf>
>

  reply	other threads:[~2010-08-01 15:33 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 21:17 3d performance very low Hanno Böck
2010-07-28 21:25 ` Matt Turner
2010-07-28 21:29   ` Hanno Böck
2010-07-29  7:43     ` Tino Keitel
2010-07-29 15:15       ` Hanno Böck
2010-07-29 16:24         ` Matt Turner
2010-07-29 16:32           ` Paul Menzel
2010-07-29 17:40           ` Philipp Klaus Krause
2010-07-29 21:47 ` Rémi Cardona
2010-07-30 13:20   ` Camassa Valerio
2010-07-30 16:42     ` Sven Arvidsson
2010-07-31  8:36       ` Valerio Camassa
2010-07-31  8:39         ` Valerio Camassa
2010-08-01 15:26           ` Robert Hooker
2010-08-01 15:33             ` Valerio Camassa [this message]
2010-07-31  9:08         ` Geir Ove Myhr
2010-07-31  9:09         ` Paul Menzel
2010-07-31  9:15           ` Valerio Camassa
2010-07-30 14:06 ` Owain Ainsworth

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=4C5593C8.8080607@gmail.com \
    --to=valerio993@gmail.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sarvatt@ubuntu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox