Displaying 4 results from an estimated 4 matches for "data_array".
Did you mean:
data_area
2006 Dec 15
5
Testing event driven Socket classes
...alid_protocol? data
return false unless data =~ /(\d{3})([^<>]*)<([^><]*)>##(.*?)##/
return true
end
# method is a callback, gets called whenever data is there in socket to read
def receive_data data
data.chomp!
while data && data.length > 0
data_array = data.split(/\r?\n/m,2)
@chunked_data << data_array[0]
data = data_array[1]
# two level of protocol handling
if @chunked_data =~ /(\d{3})(.*)<(.*)?>(##(.*)##)/
if valid_protocol?(@chunked_data)
dispatch_request
else
se...
2023 Jul 10
10
[PATCH vhost v11 00/10] virtio core prepares for AF_XDP
## About DMA APIs
Now, virtio may can not work with DMA APIs when virtio features do not have
VIRTIO_F_ACCESS_PLATFORM.
1. I tried to let DMA APIs return phy address by virtio-device. But DMA APIs just
work with the "real" devices.
2. I tried to let xsk support callballs to get phy address from virtio-net
driver as the dma address. But the maintainers of xsk may want to use
2002 Mar 01
1
plot(table..) using pairs
I'm trying to visualise relationships between a number of categorical
variables with values 0 and 1.
Plot(table(x,y))
..works well for one relationship, so I want to use this to examine all
relationships using pairs function.
pairs(data_array, upper.panel=panel.tab)
where
panel.tab <- function (x,y)
{
plot(tables(x,y))
}
..produces the error..
Error in pairs.default(a, upper.panel = panel.tab) :
The panel function made a new plot
Can anyone help..?? Many thanks
Phil.
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-...
2014 Jun 19
6
[LLVMdev] [RFC] Add compiler scheduling barriers
...pseudo-instructions with appropriate
properties(hasSideEffects for memory barrier and isTerminator for full
barrier) and a pseudo-instruction elimination pass after the
scheduling pass.
What do people think of this idea?
Cheers,
Yi
------
[1] A piece of code that requires such behaviour is:
Data_array[n] = x; // memory access
__DSB();
__WFI(); // This cannot get executed until DSB completed
Moving WFI to before DSB will cause wrong behaviour. Code is taken
from DAI0321A 4.14,
(http://infocenter.arm.com/help/topic/com.arm.doc.dai0321a/DAI0321A_programming_guide_memory_barriers_for_...