Displaying 20 results from an estimated 21 matches for "rd1".
Did you mean:
rc1
2012 Mar 07
1
extract same columns and rows in two matrices
...r both matrices. Thank you very much for all you help.
I can do it, but I am pretty sure there is a better/faster way:
################ make some sample data
ua = matrix(c(1,2,3,4,5,6),nrow=2,ncol=3)
colnames(ua) = c('a','b','c')
rownames(ua)= c('ra','rb')
rd1 = matrix(c(7,8,9,10,11,12,13,14,15,16,17,18),nrow=3,ncol=4)
colnames(rd1) = c('c','b','a','d')
rownames(rd1)= c('rc','rb','ra')
> rd1
c b a d
rc 7 10 13 16
rb 8 11 14 17
ra 9 12 15 18
> ua
a b c
ra 1 3 5
rb 2 4 6
###################...
2007 Apr 11
1
bind or samba configuration preventing browsing network
I have a networking problem where I am not certain if the problem is
samba or bind. I am still pretty much a nb at linux. The machine in
question is running openSuSE 10.2 and is named rd1. I had samba working
fine before I started to make it a WINS server and DNS host.
I have a small LAN with no real administration functionality. The
network is used for simple file sharing and dial-up internet
connectivity. The SuSE box is the only linux box on the network, and a
fairly new add...
2012 Mar 05
1
index instead of loop?
...ot;2007-06-30","2007-09-30","2007-12-31","2008-03-31","2008-06-30","2008-09-30","2008-12-31")
nms = c("A","B","C","D")
# these are the report dates that are the real days the data was available
rd1 =
matrix(c("20070514","20070814","20071115","20080213","20080514","20080814","20081114","20090217",
"20070410","20070709","20071009","20080109","20080407","2008070...
2020 Mar 23
3
[InstCombine] Addrspacecast and GEP assumed commutative
...this being a problem. I think it is valid if the gep is
inbounds but not otherwise. Matt, wdyt?
> I stumbled upon this because this reordering actually gives problems for instruction selection in the NVPTX backend.
> Without reordering, the above IR gets lowered to:
>
> ld.param.u64 %rd1, [test_param_0];
> cvta.to.global.u64 %rd2, %rd1;
> mov.u16 %rs1, 0;
> st.global.u16 [%rd2+32], %rs1;
> ret;
>
> But with the reordering, the backend instead emits this:
>
> ld.param.u64 %rd1, [test_param_0];
> add.s64 %rd2, %rd1, 32;
> cvta.to.global.u64 %rd3, %rd2;
&...
2013 Mar 15
1
order of APPEND and INITRD
Igor asked about APPEND:
> In other words: Can I break up a long line into multiple lines
> in 5.01 or 5.10pre now or is that still not supported?
I also wonder: can one control whether the INITRD parameter gets
prepended or appended? Right now it seems to be placed after APPEND
parameters, but might be more useful if it came first.
The Debian/Ubuntu installers will copy parameters
2012 Mar 03
0
removing data look-ahead, something faster.
...ot;2007-06-30","2007-09-30","2007-12-31","2008-03-31","2008-06-30","2008-09-30","2008-12-31")
nms = c("A","B","C","D")
# these are the report dates that are the real days the data was available
rd1 =
matrix(c("20070514","20070814","20071115","20080213","20080514","20080814","20081114","20090217",
"20070410","20070709","20071009","20080109","20080407","2008070...
2014 Oct 24
3
[LLVMdev] IndVar widening in IndVarSimplify causing performance regression on GPU programs
...add.s64 %rd4, %rd4, 12;
setp.lt.s32 %p2, %r6, %r3;
@%p2 bra BB0_2;
in which %r6 is the induction variable i.
With widening, the loop body becomes:
BB0_2: // =>This Inner Loop Header:
Depth=1
mul.lo.s64 %rd8, %rd10, %rd10;
st.u32 [%rd9], %rd8;
add.s64 %rd10, %rd10, 3;
add.s64 %rd9, %rd9, 12;
setp.lt.s64 %p2, %rd10, %rd1;
@%p2 bra BB0_2;
Although the number of PTX instructions in both versions are the same, the
version with widening use...
2010 Apr 07
0
question about fold function
...OD6 NEWPROD7
1 46236 1 42 0.8769 0 NA NA NA NA NA NA
2 93340 1 42 0.1926 0 NA NA NA NA NA NA
3 93340 1 43 0.0000 0 NA NA NA NA NA NA
NEWPROD8 RD1 RD2 RD3 RD4 RD5 RD6 RD7 RD8
1 NA 0 NA NA NA NA NA NA NA
2 NA 0 NA NA NA NA NA NA NA
3 NA 0 NA NA NA NA NA NA NA
> d4<-fold(d6,time='survival',event='dead',cov=c(16:23,24:31),cov.names=c('newproduct','R&D'))
Er...
2006 Sep 27
0
umask and logging in openssh
...iding ftp level logging
functionality typically available in other ftp servers to be important
security features that openssh should provide by default. Is there any
history on this that I'm not aware of?
Thanks,
-- Ralf Durkee, CISSP, GSEC, GCIH, GSNA
Principal Security Consultant
http://rd1.net
2017 Oct 11
1
[PATCH v1 01/27] x86/crypto: Adapt assembly for PIE support
...R, RKR; \
do_mask(mask);
@@ -275,9 +279,9 @@ __cast6_enc_blk8:
movq %rdi, CTX;
- vmovdqa .Lbswap_mask, RKM;
- vmovd .Lfirst_mask, R1ST;
- vmovd .L32_mask, R32;
+ vmovdqa .Lbswap_mask(%rip), RKM;
+ vmovd .Lfirst_mask(%rip), R1ST;
+ vmovd .L32_mask(%rip), R32;
inpack_blocks(RA1, RB1, RC1, RD1, RTMP, RX, RKRF, RKM);
inpack_blocks(RA2, RB2, RC2, RD2, RTMP, RX, RKRF, RKM);
@@ -301,7 +305,7 @@ __cast6_enc_blk8:
popq %rbx;
popq %r15;
- vmovdqa .Lbswap_mask, RKM;
+ vmovdqa .Lbswap_mask(%rip), RKM;
outunpack_blocks(RA1, RB1, RC1, RD1, RTMP, RX, RKRF, RKM);
outunpack_blocks(RA2, R...
2017 Jul 25
0
[Questions] About small files performance
...m=10.254.3.xx
fsd=fsd1,anchor=/mnt/smalltest1/smalltest/,depth=2,width=100,openflags=o_direct,files=100,size=64k,shared=yes
fwd=format,threads=256,xfersize=xxx
fwd=default,xfersize=xxx,fileio=random,fileselect=random,rdpct=60,threads=256
#fwd=fwd1,fsd=fsd1,host=hd1
#fwd=fwd2,fsd=fsd1,host=hd2
rd=rd1,fwd=fwd*,fwdrate=max,format=restart,elapsed=600,interval=1
1) Use *o_direct* to bypass cache
2) More than 256 threads show no affect in this test
3) Total 100 millon 64k files
#####volume info#####
Volume Name: ttt
Type: Replicate
Volume ID: cf23b1fe-d430-4ede-b33b-b54a2c04d080
Status: Started
Sn...
2013 Mar 29
1
Create values based on a table of conditions
..."PI5", "PI6",
"PI7", "PI8", "PO1", "PO10", "PO11", "PO12", "PO13", "PO2", "PO3",
"PO4", "PO5", "PO6", "PO7", "PO8", "PO9", "RD1", "RD2", "WB1"
), class = "factor"), collar = c(36L, 64L, 25L, 28L, 11L, 46L,
58L, 12L, 4L, 52L, 2L, 63L, 14L, 12L, 12L, 57L, 51L, 51L, 24L,
42L, 44L, 25L, 23L, 7L, 2L, 45L, 9L, 11L, 30L, 14L, 42L, 23L,
19L, 52L, 41L, 53L, 18L, 41L, 55L, 10L, 15L, 50L, 34L, 3L, 16...
2013 Apr 26
2
Remove reciprocal data from a grouped animal social contact dataset
...CO12
13 CO13
14 CO14
15 CO15
16 CO16
17 CO17
18 PO1
19 PO2
20 PO3
21 PO4
22 PO5
23 PO6
24 PO7
25 PO8
26 PO9
27 PO10
28 PO11
29 PO12
30 PO13
31 PI1
32 PI2
33 PI3
34 PI4
35 PI5
36 PI6
37 PI7
38 PI8
39 RD1
40 RD2
41 WB1
42 WB2
Because both collars may have recorded the single contact, I need to
remove the reciprocal contacts from this dataset. For example, you may
have records for "CO1 CO2" that are mirrored by records for "CO2 CO1".
If there are the same number of re...
2018 Mar 13
32
[PATCH v2 00/27] x86: PIE support and option to extend KASLR randomization
Changes:
- patch v2:
- Adapt patch to work post KPTI and compiler changes
- Redo all performance testing with latest configs and compilers
- Simplify mov macro on PIE (MOVABS now)
- Reduce GOT footprint
- patch v1:
- Simplify ftrace implementation.
- Use gcc mstack-protector-guard-reg=%gs with PIE when possible.
- rfc v3:
- Use --emit-relocs instead of -pie to reduce
2018 Mar 13
32
[PATCH v2 00/27] x86: PIE support and option to extend KASLR randomization
Changes:
- patch v2:
- Adapt patch to work post KPTI and compiler changes
- Redo all performance testing with latest configs and compilers
- Simplify mov macro on PIE (MOVABS now)
- Reduce GOT footprint
- patch v1:
- Simplify ftrace implementation.
- Use gcc mstack-protector-guard-reg=%gs with PIE when possible.
- rfc v3:
- Use --emit-relocs instead of -pie to reduce
2017 Oct 04
28
x86: PIE support and option to extend KASLR randomization
These patches make the changes necessary to build the kernel as Position
Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below
the top 2G of the virtual address space. It allows to optionally extend the
KASLR randomization range from 1G to 3G.
Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler
changes, PIE support and KASLR in general. Thanks to
2017 Oct 04
28
x86: PIE support and option to extend KASLR randomization
These patches make the changes necessary to build the kernel as Position
Independent Executable (PIE) on x86_64. A PIE kernel can be relocated below
the top 2G of the virtual address space. It allows to optionally extend the
KASLR randomization range from 1G to 3G.
Thanks a lot to Ard Biesheuvel & Kees Cook on their feedback on compiler
changes, PIE support and KASLR in general. Thanks to
2018 May 23
33
[PATCH v3 00/27] x86: PIE support and option to extend KASLR randomization
Changes:
- patch v3:
- Update on message to describe longer term PIE goal.
- Minor change on ftrace if condition.
- Changed code using xchgq.
- patch v2:
- Adapt patch to work post KPTI and compiler changes
- Redo all performance testing with latest configs and compilers
- Simplify mov macro on PIE (MOVABS now)
- Reduce GOT footprint
- patch v1:
- Simplify ftrace
2017 Oct 11
32
[PATCH v1 00/27] x86: PIE support and option to extend KASLR randomization
Changes:
- patch v1:
- Simplify ftrace implementation.
- Use gcc mstack-protector-guard-reg=%gs with PIE when possible.
- rfc v3:
- Use --emit-relocs instead of -pie to reduce dynamic relocation space on
mapped memory. It also simplifies the relocation process.
- Move the start the module section next to the kernel. Remove the need for
-mcmodel=large on modules. Extends
2017 Oct 11
32
[PATCH v1 00/27] x86: PIE support and option to extend KASLR randomization
Changes:
- patch v1:
- Simplify ftrace implementation.
- Use gcc mstack-protector-guard-reg=%gs with PIE when possible.
- rfc v3:
- Use --emit-relocs instead of -pie to reduce dynamic relocation space on
mapped memory. It also simplifies the relocation process.
- Move the start the module section next to the kernel. Remove the need for
-mcmodel=large on modules. Extends