All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Marcin Kościelnicki" <koriakin-mP9o5jsk0RY@public.gmane.org>
To: Matthew Kolar <broken.shakles-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: I would like to offer my help.
Date: Sun, 13 Nov 2011 02:10:11 +0100	[thread overview]
Message-ID: <651aafd4627d45a8dd835885dcdd9ffd@0x04.net> (raw)
In-Reply-To: <4EBF2106.603-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

> Hello, Nouveau devs!
>
>  I would like you to know that I have a laptop with 2 Geforce GTX
> 285m cards on board in an SLI config, I know the SLI part is not
> relevant at this point, but I still would like to offer my rig for
> testing single card configs.  If you want to walk me thru what you
> need me to do, just shoot me an email.
>
> Matthew Kolar

This sounds like a perfect configuration to RE the inter-GPU 
communication used by GPUdirect. I don't have time right now to look at 
it, but I should be able to prepare some good instructions next week. 
Basically we'd need to do a combo mmiotrace + valgrind-mmt trace of a 
CUDA application utilising GPUdirect calls in various modes.

The 3d SLI functionality, as tested by me on double-nv50 under linux, 
appears to be implemented entirely using "normal" features - the special 
inter-GPU transfer circuitry is set up, but never actually used. May 
still be worth a trace on nvc0, though.

Marcin Kościelnicki
_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

      parent reply	other threads:[~2011-11-13  1:10 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-13  1:44 I would like to offer my help Matthew Kolar
     [not found] ` <4EBF2106.603-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-11-13  1:10   ` Marcin Kościelnicki [this message]

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=651aafd4627d45a8dd835885dcdd9ffd@0x04.net \
    --to=koriakin-mp9o5jsk0ry@public.gmane.org \
    --cc=broken.shakles-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /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.