search for: aggregrates

Hi, the ArgumentPromotion pass replaces aggregrate function arguments by multiple individual arguments. The default pass only does this when the aggregrate has 3 or less elements, otherwise the code will be unchanged. I have a need to always promote aggregrate arguments, even when there are a lot of them. The attached patch adds a "maxElements" argument to ArgPromotion's

...now that structs are a first class values, the old way or returning multiple values is a bit confusing. The old way had a variable number of arguments to the return instruction, which could come out at the caller end as some special aggregrate value that could be indexed using getresult. Now that aggregrates are first class, you should be able to simply return a single struct and access the result in the caller using the new extractvalue instruction. However, both approaches define a function with a struct as a return type: It's not possible to tell the difference between both from looking at the...

Hi, I have to recognize that i don't fully understand the aggregate function, but i think it should help me with what i want to do. xveg is a data.frame with location, species, and total for the species. Each location is repeated, once for every species present at that location. For each location i want to find out which species has the maximum total ... so i've tried different ways to

...he current form of the ret instruction is still > useful, for > making multiple return values readable. In particular, writing > ret i32 1, i32 2 > is a lot more readable than the (functionally identical) three line > return > statement above. However, to make the first class aggregrates even > more > usable, it might be better to remove the multi operand return > instruction and > add support for literal aggregrates. Currently, I think these are only > supported as global constants. It would be useful if the following > was valid: > ret { i32, i32 } { i...

Hello R experts, I'm trying to test R in a shared memory environment in which addressable memory is aggregrated to about 600G. However, I get an error of 'too many elements' specified when I try creating a 45K x 100K matrix. I tried running R with a --max-nsize=50000000000 option, but got the same message. Is there a way to run create such large matrices? thanks, Paul Rodriguez

On Fri, 26 Jan 2018 15:30:35 -0800, Samudrala, Sridhar wrote: > On 1/26/2018 2:47 PM, Jakub Kicinski wrote: > > On Sat, 27 Jan 2018 00:14:20 +0200, Michael S. Tsirkin wrote: > >> On Fri, Jan 26, 2018 at 01:46:42PM -0800, Siwei Liu wrote: > >>>> and the VM is not expected to do any tuning/optimizations on the VF driver > >>>> directly, >

...truction is still > > useful, for > > making multiple return values readable. In particular, writing > > ret i32 1, i32 2 > > is a lot more readable than the (functionally identical) three line > > return > > statement above. However, to make the first class aggregrates even > > more > > usable, it might be better to remove the multi operand return > > instruction and > > add support for literal aggregrates. Currently, I think these are only > > supported as global constants. It would be useful if the following > > was val...

On Sat, 27 Jan 2018 00:14:20 +0200, Michael S. Tsirkin wrote: > On Fri, Jan 26, 2018 at 01:46:42PM -0800, Siwei Liu wrote: > > > and the VM is not expected to do any tuning/optimizations on the VF driver > > > directly, > > > i think the current patch that follows the netvsc model of 2 netdevs(virtio > > > and vf) should > > > work fine. > >

Hi everyone, I am writing a simple script to read in a data file, search through the data file for an exact character match for a microRNA name, subset those rows, and aggregrate a dataframe with those subselections all in a for loop. This is what I have so far: #READ IN DATA file1 = "C:/Desktop/mirtarget2_predictions.txt" data = read.table(file1, header=FALSE, sep="\t")

Hi, I am trying to use the update_attributes on object with nested attributes and I am getting the following error: ProductPrice expected, got HashWithIndifferentAccess Here''s the situation (simplified): class Product < ActiveRecord::Base belongs_to :productPrice end class ProductPrice < ActiveRecord::Base has_one :product, :dependent => true

On 1/26/2018 2:47 PM, Jakub Kicinski wrote: > On Sat, 27 Jan 2018 00:14:20 +0200, Michael S. Tsirkin wrote: >> On Fri, Jan 26, 2018 at 01:46:42PM -0800, Siwei Liu wrote: >>>> and the VM is not expected to do any tuning/optimizations on the VF driver >>>> directly, >>>> i think the current patch that follows the netvsc model of 2 netdevs(virtio

It was found when running fio sequential write test with a XFS ramdisk on a KVM guest running on a 2-socket x86-64 system, the %CPU times as reported by perf were as follows: 69.75% 0.59% fio [k] down_write 69.15% 0.01% fio [k] call_rwsem_down_write_failed 67.12% 1.12% fio [k] rwsem_down_write_failed 63.48% 52.77% fio [k] osq_lock 9.46% 7.88% fio [k]

It was found when running fio sequential write test with a XFS ramdisk on a KVM guest running on a 2-socket x86-64 system, the %CPU times as reported by perf were as follows: 69.75% 0.59% fio [k] down_write 69.15% 0.01% fio [k] call_rwsem_down_write_failed 67.12% 1.12% fio [k] rwsem_down_write_failed 63.48% 52.77% fio [k] osq_lock 9.46% 7.88% fio [k]

It was found when running fio sequential write test with a XFS ramdisk on a VM running on a 2-socket x86-64 system, the %CPU times as reported by perf were as follows: 69.75% 0.59% fio [k] down_write 69.15% 0.01% fio [k] call_rwsem_down_write_failed 67.12% 1.12% fio [k] rwsem_down_write_failed 63.48% 52.77% fio [k] osq_lock 9.46% 7.88% fio [k]

It was found when running fio sequential write test with a XFS ramdisk on a VM running on a 2-socket x86-64 system, the %CPU times as reported by perf were as follows: 69.75% 0.59% fio [k] down_write 69.15% 0.01% fio [k] call_rwsem_down_write_failed 67.12% 1.12% fio [k] rwsem_down_write_failed 63.48% 52.77% fio [k] osq_lock 9.46% 7.88% fio [k]

On Fri, 26 Jan 2018 18:30:03 -0800 Jakub Kicinski <kubakici at wp.pl> wrote: > On Fri, 26 Jan 2018 15:30:35 -0800, Samudrala, Sridhar wrote: > > On 1/26/2018 2:47 PM, Jakub Kicinski wrote: > > > On Sat, 27 Jan 2018 00:14:20 +0200, Michael S. Tsirkin wrote: > > >> On Fri, Jan 26, 2018 at 01:46:42PM -0800, Siwei Liu wrote: > > >>>> and

I'm very new to R, so please forgive me if I just missed the answer in existing documentation... I have a data set with at least three columns, X, Y, and Z. I want to produce a chart where one axis shows all the unique values of X, and the other axis shows all the unique values of Y. Each cell within the chart should contain the result of applying an aggregate function (such as mean(), for

...ill >>> useful, for >>> making multiple return values readable. In particular, writing >>> ret i32 1, i32 2 >>> is a lot more readable than the (functionally identical) three line >>> return >>> statement above. However, to make the first class aggregrates even >>> more >>> usable, it might be better to remove the multi operand return >>> instruction and >>> add support for literal aggregrates. Currently, I think these are >>> only >>> supported as global constants. It would be useful if the fol...

On 1/26/2018 6:30 PM, Jakub Kicinski wrote: > On Fri, 26 Jan 2018 15:30:35 -0800, Samudrala, Sridhar wrote: >> On 1/26/2018 2:47 PM, Jakub Kicinski wrote: >>> On Sat, 27 Jan 2018 00:14:20 +0200, Michael S. Tsirkin wrote: >>>> On Fri, Jan 26, 2018 at 01:46:42PM -0800, Siwei Liu wrote: >>>>>> and the VM is not expected to do any tuning/optimizations on

It was found when running fio sequential write test with a XFS ramdisk on a 2-socket x86-64 system, the %CPU times as reported by perf were as follows: 71.27% 0.28% fio [k] down_write 70.99% 0.01% fio [k] call_rwsem_down_write_failed 69.43% 1.18% fio [k] rwsem_down_write_failed 65.51% 54.57% fio [k] osq_lock 9.72% 7.99% fio [k] __raw_callee_save___kvm_vcpu_is_preempted 4.16%