similar to: [PATCH] nv50/ir: rebase indirect temp arrays to 0, so that we use less lmem space

Previously we were treating any indirect temp array usage to mean that everything should end up in lmem. The MemoryOpt pass would clean a lot of that up later, but in the meanwhile we would lose a lot of opportunity for optimization. This helps a lot of Metro 2033 Redux and a handful of KSP shaders: total instructions in shared programs : 6288373 -> 6261517 (-0.43%) total gprs used in shared

On 1/29/2015 7:21 PM, Jatin Davey wrote: > [root at localhost ~]# lspci | grep RAID > 05:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS-3 > 3108 [Invader] (rev 02) to get info out of those, you need to install MegaCli64 from LSI Logic, which has the ugliest command lines and output you've ever seen. I use the python script below, which I put in

On 2/16/2016 3:23 PM, Zube wrote: > Does anyone know what program can be used to query the RAID status > from the OS for an on-board LSI SAS 2308-4i? the 2308 isn't actually a megaraid, its a simple SAS HBA that has an optional raid mode IF its flashed with IR firmware... this only supports raid 0/1/10. I always(!) flash these with the IT firmware that turns them back into a

On 1/30/2015 9:44 AM, John R Pierce wrote: > On 1/29/2015 7:21 PM, Jatin Davey wrote: >> [root at localhost ~]# lspci | grep RAID >> 05:00.0 RAID bus controller: LSI Logic / Symbios Logic MegaRAID SAS-3 >> 3108 [Invader] (rev 02) > > to get info out of those, you need to install MegaCli64 from LSI > Logic, which has the ugliest command lines and output you've

Use the dst temp variable which was used in the TGSI_FILE_OUTPUT case everywhere. This makes the code somewhat easier to reads and helps avoiding going over 80 chars with upcoming changes. This also brings the dst handling more in line with the src handling. Signed-off-by: Hans de Goede <hdegoede at redhat.com> --- src/gallium/drivers/nouveau/codegen/nv50_ir_from_tgsi.cpp | 12

Hi all, I have a dataset which includes 84 rows and 4313 columns. Starting from the 2nd row, each row represents a patient. The 1st column is for "arrayID" 2nd column is for "time" 3rd column is for "cancer" 4th column is for "patientID" Starting for the 5th columns, each

Dear R-devel When 'install.packages' runs, it updates all html files in all packages. Mostly, there seems to be no actual change to the html file contents, but the date/time does change. This has causing been me a bit of trouble, because I keep synchronized versions of R on several different machines, and whenever I install a package, many MB of file transfers are required; my slow upload

Add support for OpenCL global memory buffers, note this has only been tested with regular load and stores and likely needs more work for e.g. atomic ops. Signed-off-by: Hans de Goede <hdegoede at redhat.com> --- src/gallium/drivers/nouveau/codegen/nv50_ir.h | 1 + .../drivers/nouveau/codegen/nv50_ir_emit_gk110.cpp | 31 +++++++++++++++++-----

R-help, I would like to place nine (3X3) plots per page. I am not properly implement mfrow(3,3) in the script below: jpeg("xyplot.jpg") #names output file my_args <- commandArgs() #sets up to take args from dos batch command mfcol(3,3) #set page for 3X3 TEMPS <- c(-15,25,85)#list of temps VBATS <- c(3,3.6,4.7)#list of Bats BOARDS <-

Hi, On 16-03-16 11:37, Samuel Pitoiset wrote: > Could you please get rid of the cosmetic changes (eg. the switch ones)? > Because this doesn't really improve readability and in my opinion these changes should be eventually done in a separate patch. I need at least halve of those cosmetic changes, because half of them is not cosmetic, e.g. : - case FILE_MEMORY_BUFFER: code[1] =

Could you please get rid of the cosmetic changes (eg. the switch ones)? Because this doesn't really improve readability and in my opinion these changes should be eventually done in a separate patch. Other than that, this patch is : Reviewed-by: Samuel Pitoiset <samuel.pitoiset at gmail.com> Yes, this probably won't work as is for atomic operations but the lowering pass is

Does anyone know what program can be used to query the RAID status from the OS for an on-board LSI SAS 2308-4i? On this page: http://docs.avagotech.com/docs/12351997 there is a curious note on the left that reads: "Integrated MegaRAID support available upon request" After one mostly fruitless round of chatting with LSI/Avago/Broadcom and one completely fruitless round of chatting

On 1/30/2015 1:53 AM, Gordon Messmer wrote: > On 01/29/2015 05:07 AM, Jatin Davey wrote: >> Yes , it is a SATA disk. I am not sure of the speed. Can you tell me >> how to find out this information ? Additionally we are using RAID 10 >> configuration with 4 disks. > > What RAID controller are you using? > > # lspci | grep RAID [Jatin] [root at localhost ~]# lspci |

On Thursday 02 November 2017 14:10:25 Bowie Bailey wrote: > If you want raid 5 or 6, then you should get a hardware controller. For > raid 1, mdadm should work just fine.? I would suggest trying it before > buying a raid controller.? If it works for you, you save a few hundred > dollars and you have one less piece of hardware to worry about. > > I haven't looked at them in

I just had an IBM in a remote location with a hardware raid1 have both drives go bad. With local machines I probably would have caught it from the drive light before the 2nd one died... What is the state of the art in linux software monitoring for this? Long ago when that box was set up I think the best I could have done was a Java GUI tool that IBM had for their servers - and that seemed like

tgsi_default_instruction_memory / tgsi_build_instruction_memory were returning uninitialized memory for tgsi_instruction_memory.Texture and tgsi_instruction_memory.Format. Note 0 means not set, and thus is a correct default initializer for these. Fixes: 3243b6fc97 ("tgsi: add Texture and Format to tgsi_instruction_memory") Cc: Nicolai Hähnle <nicolai.haehnle at amd.com>

Some of the lowering steps we currently do for FILE_MEMORY_GLOBAL only apply to buffers, making it impossible to use FILE_MEMORY_GLOBAL for OpenCL global buffers. This commits changes the buffer code to use FILE_MEMORY_BUFFER at the ir_from_tgsi and lowering steps, freeing use of FILE_MEMORY_GLOBAL for use with OpenCL global buffers. Note that after lowering buffer accesses use the

From 43e0635d7d90f65055d1f49d998974041315f4fc Mon Sep 17 00:00:00 2001 From: Shao Miller <shao.miller at yrdsb.edu.on.ca> Date: Fri, 11 Dec 2009 01:26:59 +0000 Subject: [PATCH] memdisk: Fix "might be used uninitialized" warnings The checksum_buf function was providing an incorrect checksum on at least one build. Signed-off-by: Shao Miller <shao.miller at yrdsb.edu.on.ca>

OK, so there's a bunch of stuff in here. The geometry stuff is based on the work started by Bryan Cain and Christoph Bumiller. Patches 01-12: Add support for geometry shaders and fix related issues Patches 13-14: Make it possible for fb clears to operate on texture attachments with an explicit layer set (as is allowed in gl 3.2). Patches 15-17: Make ARB_texture_multisample work

This is enough to enable tessellation support on nvc0. It seems to work a lot better on my GF108 than GK208. I suspect that there's some sort of scheduling shenanigans that need to be adjusted for kepler+. Or perhaps some shader header things. Even with the GF108, I still get occasional blue triangles in Heaven, but I get a *ton* of them on the GK208 -- seemingly the same issue, but it's