similar to: o2locktop introduction

Good News. Thanks. > -----????----- > ???: ocfs2-users-bounces at oss.oracle.com > [mailto:ocfs2-users-bounces at oss.oracle.com] ?? Gang He > ????: 2019?3?20? 18:07 > ???: ocfs2-devel at oss.oracle.com; ocfs2-tools-devel at oss.oracle.com; > ocfs2-users at oss.oracle.com > ??: [Ocfs2-users] o2locktop introduction > > Hello Guys, > > We wrote a tool with

Good News. Thanks. > -----????----- > ???: ocfs2-users-bounces at oss.oracle.com > [mailto:ocfs2-users-bounces at oss.oracle.com] ?? Gang He > ????: 2019?3?20? 18:07 > ???: ocfs2-devel at oss.oracle.com; ocfs2-tools-devel at oss.oracle.com; > ocfs2-users at oss.oracle.com > ??: [Ocfs2-users] o2locktop introduction > > Hello Guys, > > We wrote a tool with

Hi Charles, The battery.mfr.date is actually the correct value I'm looking for. That is the exact date the battery was last replaced. And yes, it is the correct value displayed in apcupsd. For the debug commands, is there a line break between "upsdrvctl stop" and "/usr/local/libexec/nut/usbhid-ups -a APC_BR1500GI -DDDDD 2>&1 | tee /tmp/APC_BR1500GI.debug.txt"?

No segfault but a BIG warning from the compiler. That's because dereferencing the pointer inside your myfunc() function will produce an int that is not predictable i.e. it is system-dependent. Its value will depend on sizeof(long int) (which is not guaranteed to be 8) and on the endianness of the system. Also if the pointer you pass in the call to the function is an array of long ints, then

Hi Andreas, note that with the introduction of ALTREP, as far as I understand, calls as "simple" as DATAPTR can execute arbitrary code (R or native). Even without ALTREP, if you execute user-provided R code via Rf_eval and such on some custom thread, you may end up executing native code of some package, which may assume it is executed only from the R main thread. Could you (1)

Thanks for the replies and for confirming my suspicion. Interestingly, src/include/S.h uses a trick: ?? #define longint int and so does the nlme package (within src/init.c). On 08/15/2018 02:47 PM, Herv? Pag?s wrote: > No segfault but a BIG warning from the compiler. That's because > dereferencing the pointer inside your myfunc() function will > produce an int that is not

Stepan, Andreas gave a lot more thought into what you question in your reply. His question was how you can avoid what you where proposing and have proper threading under safe conditions. Having dealt with this before, I think Andreas' write up is pretty much the most complete analysis I have seen. I'd wait for Luke to chime in as the ultimate authority if he gets to it. The

On 7/7/19 17:41, Jialin Ma wrote: > Hi Abby, > > Thanks a lot for your paraphrasing and your suggestion! > > The problem of wrapping the list into a S3/S4 object, i.e. subclassing array > or matrix, is that one also has to define a bunch of methods for subsetting, > joining, etc, in order to make it behave like a list array. The reason is that > most R functions for

On 7/24/19 12:25 PM, john.hubbard at gmail.com wrote: > From: John Hubbard <jhubbard at nvidia.com> > > Hi, > > This is mostly Jerome's work, converting the block/bio and related areas > to call put_user_page*() instead of put_page(). Because I've changed > Jerome's patches, in some cases significantly, I'd like to get his > feedback before we

On Tue, Mar 19, 2019 at 02:38:06PM +0200, Liran Alon wrote: > Hi Michael, > > Great blog-post which summarise everything very well! > > Some comments I have: Thanks! I'll try to update everything in the post when I'm not so jet-lagged. > 1) I think that when we are using the term ?1-netdev model? on community discussion, we tend to refer to what you have defined in

Hi Michael, Great blog-post which summarise everything very well! Some comments I have: 1) I think that when we are using the term ?1-netdev model? on community discussion, we tend to refer to what you have defined in blog-post as "3-device model with hidden slaves?. Therefore, I would suggest to just remove the ?1-netdev model? section and rename the "3-device model with hidden

> On 15 Aug 2018, at 12:48, Duncan Murdoch <murdoch.duncan at gmail.com> wrote: > >> On 15/08/2018 7:08 AM, Benjamin Tyner wrote: >> Hi >> In my R package, imagine I have a C function defined: >> void myfunc(int *x) { >> // some code >> } >> but when I call it, I pass it a pointer to a longint instead of a >> pointer to an

On Aug 30, 2018, at 6:54 AM, Ong, Kevin wrote: > > I'm very sorry for the delay here, I've been very swamped with work. Here's the relevant information you guys need: > > "upsc APC_BR1500GI" output: https://pastebin.com/rH3W0dbz > "upsrw APC_BR1500GI" output: https://pastebin.com/tEWv8a3d > "upscmd -l APC_BR1500GI" output:

R's checks seem to be failing to notice a redundant '...' argument described in the documentation of a function. Consider a function: fun_3 <- function(arg1, arg2, arg3) { "I am fun_3" } If its documentation describes an argument, say 'dummy', R check reports something like: * checking Rd \usage sections ... WARNING Documented arguments not in \usage in

I'm running a bit late with the e-mail this time around, but I think that's ok since there really isn't any major new features here - the bulk of the Ocfs2 update is bug fixes, or cleanups. The same goes for configfs. The only two things that could be described as features would be: - Sunil has updated Ocfs2 to provide even more live cluster locking information via debugfs. - Joel

Thanks a lot Jiefei, I had thought of defining a binary operator (inspired by pipes) or simply using an additional condition in the if() calls [e.g. if(foo & fn(bar)) doSomeThing; with fn(bar) returning a logical], but both are workaround that I do not find as elegant as a proper control-flow construct. Thus two questions remain: - is it possible to create a control-flow construct in pure R?

Hi, As the subject suggests, I am looking for the most robust way to call an (arbitrary) function from the R API from another but the main POSIX thread in a package's code. I know that, "[c]alling any of the R API from threaded code is ?for experts only? and strongly discouraged. Many functions in the R API modify internal R data structures and might corrupt these data structures if

Hi Abby, Thanks a lot for your paraphrasing and your suggestion! The problem of wrapping the list into a S3/S4 object, i.e. subclassing array or matrix, is that one also has to define a bunch of methods for subsetting, joining, etc, in order to make it behave like a list array. The reason is that most R functions for subsetting, joining, etc. do not preserve class attributes of the input, which

Hi all, I've put up a blog post with a summary of where network device failover stands and some open issues. Not sure where best to host it, I just put it up on blogspot: https://mstsirkin.blogspot.com/2019/03/virtio-network-device-failover-support.html Comments, corrections are welcome! -- MST

Hi all, I've put up a blog post with a summary of where network device failover stands and some open issues. Not sure where best to host it, I just put it up on blogspot: https://mstsirkin.blogspot.com/2019/03/virtio-network-device-failover-support.html Comments, corrections are welcome! -- MST