search for: uncessary

...> + memset(&udata, 0, sizeof(udata)); > + udata.AcceptPromiscuous = TRUE; > + udata.AcceptAnyPort = TRUE; Why promiscuous? That seems to want to accept it on any local address and put the NIC into promiscuous mode, avoiding the default MAC filter in the NIC. This should be uncessary as we're not capturinig. > +/** > + * Establish a connection on an open socket > + * > + * @param:socket, the open socket > + * @param:ip, the ip address > + * @param:port, the port number, host-byte order > + */ > +void core_udp_connect(struct pxe_pvt_inode *socket, ui...

>>> > > Why promiscuous?? That seems to want to accept it on any local address > and put the NIC into promiscuous mode, avoiding the default MAC filter > in the NIC.? This should be uncessary as we're not capturinig. If I remember correctly, this was required for TFTP boot because otherwise it's impossible to accept DHCP packets when we have no IP address assigned. I'm not suggesting that is the intention of the AcceptPromiscuous flag, only that it was the observed beh...

...gle observation, which has the closest date of 'OBS_DATE' to 'IDX_DT'. For example, for 'PT_ID' of 4549, I need row 13, of which the OBS_DATE is just one day away from IDX_DT. I was thinking about using abs(), and I got this: baseline<- function(x){ + + #remove all uncessary variables + baseline<- x[,c("PT_ID","DAYS_DIFF")] + + #get a list of every unique ID + uniqueID <- unique(baseline$PT_ID) + + #make a vector that will contain the smallest DAYS_DIFF + first <- rep(-99,length(uniqueID)) + + i = 1 + #loop through each unique...

...; effect. What is this register used for? > > > > 100c1c is one of three registers which control the (upper bits of > > the > > 32-byte > > aligned) memory locations that the pollers use: So, as the memory location is 32-byte aligned the last 8 bits of the address are uncessary. 100c1c and the others hold 32 bits. So are the missing 24 bits of the address forced to zero or do we need to specify them somewhere? Here is the patch so far, where priv->r100c08 is an address to an empty dma page: diff --git a/nvkm/subdev/fb/nv50.c b/nvkm/subdev/fb/nv50.c index 4150...

...242c43415eccd008b90c812f3d04b398d Don''t unshadow when the shadow l2 is the current used shadow table. Otherwise, when destorying the domain, if the current sl2 is unpinned, the shadow page will be freed without accquire the shadow_lock. This may also improve the performance due to avoiding uncessary unshadow. Signed-off-by: Xiaofeng Ling <xiaofeng.ling@intel.com> _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...bly is the same in S. The last time I tried to use rbind in R, it screwed up the data frame if the data frame contained dates or character vectors. Apparently that has been changed. Although there is still no reason why merge should not work in the case where all vectors are in common. It's an uncessary restriction which isn't even mentioned in the function information as far as I can see. Rick Bilonick Don MacQueen wrote: > A side-by-side, or relational, merge of two data frames with exactly > the same set of variables doesn't make any sense. Perhaps you wanted > an end-to-end...

...0, sizeof(udata)); > > + udata.AcceptPromiscuous = TRUE; > > + udata.AcceptAnyPort = TRUE; > > Why promiscuous? That seems to want to accept it on any local address > and put the NIC into promiscuous mode, avoiding the default MAC filter > in the NIC. This should be uncessary as we're not capturinig. If I remember correctly, this was required for TFTP boot because otherwise it's impossible to accept DHCP packets when we have no IP address assigned. I'm not suggesting that is the intention of the AcceptPromiscuous flag, only that it was the observed behaviou...

...will be recognized as "address-not-taken". S2) Compiler may generate some global variables for some special purpose or for some special languages. These global variables are normally directly accessed. Compiler can mark the variable "addr-not-taken" to avoid uncessary alias. We would otherwise need to introduce a special meta-data for this purpose. Go back to semantic 3). At the moment a compiler generate such variables, it does not physically "see" all the reference of these vars, however it is pretty sure how these these v...

(Sending it to the correct Nvidia mailing list, sorry for the spam) Hi, When using acceleration with Nouveau on MacBook Pros with an 9400M (NVAC) card, a PFIFO interrupt 0x00400000 is thrown during the initialisation of that card (sometime after PFIFO and PGRAPH initialisation) and the laptop will lockup [1], forcing users to load Nouveau without acceleration. After some investigation, I found

...uot;address-not-taken". > > S2) Compiler may generate some global variables for some special > purpose or for some > special languages. These global variables are normally directly > accessed. Compiler > can mark the variable "addr-not-taken" to avoid uncessary > alias. > We would otherwise > need to introduce a special meta-data for this purpose. > > Go back to semantic 3). At the moment a compiler generate such > variables, > it does not physically "see" all the reference of these vars, > howeve...

change from v6: fix typos and remove uncessary comments. change from v5: spilt x86/kvm patch into guest/host part. introduce kvm_write_guest_offset_cached. fix some typos. rebase patch onto 4.9.2 change from v4: spilt x86 kvm vcpu preempted check into two patches. add documentation patch. add x86 vcpu preempted check patch under xen add...

change from v6: fix typos and remove uncessary comments. change from v5: spilt x86/kvm patch into guest/host part. introduce kvm_write_guest_offset_cached. fix some typos. rebase patch onto 4.9.2 change from v4: spilt x86 kvm vcpu preempted check into two patches. add documentation patch. add x86 vcpu preempted check patch under xen add...