search for: unlearn

...> >> Neither get_config nor set_config are expected to fail. > > > > AFAIK this is currently not a problem. According to > > http://lwn.net/Articles/627419/ these kmalloc calls never > > fail because they allocate less than a page. > > I strongly suggest you unlearn that fact. > The fix for this is in two parts: > > 1) Annotate using sched_annotate_sleep() and add a comment: we may spin > a few times in low memory situations, but this isn't a high > performance path. > > 2) Handle get_config (and other) failure in some more ele...

...> >> Neither get_config nor set_config are expected to fail. > > > > AFAIK this is currently not a problem. According to > > http://lwn.net/Articles/627419/ these kmalloc calls never > > fail because they allocate less than a page. > > I strongly suggest you unlearn that fact. > The fix for this is in two parts: > > 1) Annotate using sched_annotate_sleep() and add a comment: we may spin > a few times in low memory situations, but this isn't a high > performance path. > > 2) Handle get_config (and other) failure in some more ele...

...d to fail. > > > > > > > > AFAIK this is currently not a problem. According to > > > > http://lwn.net/Articles/627419/ these kmalloc calls never > > > > fail because they allocate less than a page. > > > > > > I strongly suggest you unlearn that fact. > > > The fix for this is in two parts: > > > > > > 1) Annotate using sched_annotate_sleep() and add a comment: we may spin > > > a few times in low memory situations, but this isn't a high > > > performance path. > > > &g...

...d to fail. > > > > > > > > AFAIK this is currently not a problem. According to > > > > http://lwn.net/Articles/627419/ these kmalloc calls never > > > > fail because they allocate less than a page. > > > > > > I strongly suggest you unlearn that fact. > > > The fix for this is in two parts: > > > > > > 1) Annotate using sched_annotate_sleep() and add a comment: we may spin > > > a few times in low memory situations, but this isn't a high > > > performance path. > > > &g...

...y understanding was that LLD was always intended to be a fully integrated LLVM project much like Clang, with a shared coding standard to go with the shared support libraries. Can we start that migration? I'm really opposed to having folks learn two styles of development, only to turn around and unlearn one shortly thereafter. To be clear, I'm not asking for help. =] Happy to do all the legwork, and if it really shouldn't be done eagerly, happy to do it as folks touch a file or interface. I'd just like to start moving things over. -Chandler -------------- next part -------------- An...

On Thu, 26 Feb 2015 11:50:42 +1030 Rusty Russell <rusty at rustcorp.com.au> wrote: > Thomas Huth <thuth at linux.vnet.ibm.com> writes: > > Hi all, > > > > with the recent kernel 3.19, I get a kernel warning when I start my > > KVM guest on s390 with virtio balloon enabled: > > The deeper problem is that virtio_ccw_get_config just silently fails on

On Thu, 26 Feb 2015 11:50:42 +1030 Rusty Russell <rusty at rustcorp.com.au> wrote: > Thomas Huth <thuth at linux.vnet.ibm.com> writes: > > Hi all, > > > > with the recent kernel 3.19, I get a kernel warning when I start my > > KVM guest on s390 with virtio balloon enabled: > > The deeper problem is that virtio_ccw_get_config just silently fails on

...xpected to fail. > >> > > >> > AFAIK this is currently not a problem. According to > >> > http://lwn.net/Articles/627419/ these kmalloc calls never > >> > fail because they allocate less than a page. > >> > >> I strongly suggest you unlearn that fact. > >> The fix for this is in two parts: > >> > >> 1) Annotate using sched_annotate_sleep() and add a comment: we may spin > >> a few times in low memory situations, but this isn't a high > >> performance path. > >> > &gt...

...xpected to fail. > >> > > >> > AFAIK this is currently not a problem. According to > >> > http://lwn.net/Articles/627419/ these kmalloc calls never > >> > fail because they allocate less than a page. > >> > >> I strongly suggest you unlearn that fact. > >> The fix for this is in two parts: > >> > >> 1) Annotate using sched_annotate_sleep() and add a comment: we may spin > >> a few times in low memory situations, but this isn't a high > >> performance path. > >> > &gt...

...> > AFAIK this is currently not a problem. According to > > > > > > http://lwn.net/Articles/627419/ these kmalloc calls never > > > > > > fail because they allocate less than a page. > > > > > > > > > > I strongly suggest you unlearn that fact. > > > > > The fix for this is in two parts: > > > > > > > > > > 1) Annotate using sched_annotate_sleep() and add a comment: we may spin > > > > > a few times in low memory situations, but this isn't a high > > >...

...> > AFAIK this is currently not a problem. According to > > > > > > http://lwn.net/Articles/627419/ these kmalloc calls never > > > > > > fail because they allocate less than a page. > > > > > > > > > > I strongly suggest you unlearn that fact. > > > > > The fix for this is in two parts: > > > > > > > > > > 1) Annotate using sched_annotate_sleep() and add a comment: we may spin > > > > > a few times in low memory situations, but this isn't a high > > >...

...y understanding was that LLD was always intended to be a fully integrated LLVM project much like Clang, with a shared coding standard to go with the shared support libraries. Can we start that migration? I'm really opposed to having folks learn two styles of development, only to turn around and unlearn one shortly thereafter. Before suggesting a massive and vague changes across someone else's code base, perhaps you should start with specific issues you see. And why you think one way is better than another way. The LLVM family of projects have a range of coding conventions. libc++, lldb, a...

I hear you - but it seems that the choice is between (a) limiting "scp" functionality to address the security vulnerability, and (b) killing "scp" altogether. I'd much prefer (a), even if it means I lose "scp remotehost:foo\* .". Especially, since (almost always) I have equal privileges on both local and remote hosts, so in that case I just originate that

...e about R, other than he had "enormous difficulties" learning it that he had especially found the documentation lacking. I dove in and started learning R. It was incredibly hard work, most of which was caused by my expectations of how I thought it ought to work. I did have a lot to "unlearn" but once I figured a certain step out, I could see that explaining it to another SAS or SPSS user would be relatively easy. I started keeping notes on these differences for myself initially. I finally posted them on the Internet as the first version of *R for SAS and SPSS Users*. It was only...

...ly fails on >> OOM. >> >> Neither get_config nor set_config are expected to fail. > > AFAIK this is currently not a problem. According to > http://lwn.net/Articles/627419/ these kmalloc calls never > fail because they allocate less than a page. I strongly suggest you unlearn that fact. The fix for this is in two parts: 1) Annotate using sched_annotate_sleep() and add a comment: we may spin a few times in low memory situations, but this isn't a high performance path. 2) Handle get_config (and other) failure in some more elegant way. Cheers, Rusty.

...fig nor set_config are expected to fail. > > > > > > AFAIK this is currently not a problem. According to > > > http://lwn.net/Articles/627419/ these kmalloc calls never > > > fail because they allocate less than a page. > > > > I strongly suggest you unlearn that fact. > > The fix for this is in two parts: > > > > 1) Annotate using sched_annotate_sleep() and add a comment: we may spin > > a few times in low memory situations, but this isn't a high > > performance path. > > > > 2) Handle get_config (...

...> > > > > > AFAIK this is currently not a problem. According to > > > > > http://lwn.net/Articles/627419/ these kmalloc calls never > > > > > fail because they allocate less than a page. > > > > > > > > I strongly suggest you unlearn that fact. > > > > The fix for this is in two parts: > > > > > > > > 1) Annotate using sched_annotate_sleep() and add a comment: we may spin > > > > a few times in low memory situations, but this isn't a high > > > > performance...

...et_config nor set_config are expected to fail. >> > >> > AFAIK this is currently not a problem. According to >> > http://lwn.net/Articles/627419/ these kmalloc calls never >> > fail because they allocate less than a page. >> >> I strongly suggest you unlearn that fact. >> The fix for this is in two parts: >> >> 1) Annotate using sched_annotate_sleep() and add a comment: we may spin >> a few times in low memory situations, but this isn't a high >> performance path. >> >> 2) Handle get_config (and oth...

...ly fails on >> OOM. >> >> Neither get_config nor set_config are expected to fail. > > AFAIK this is currently not a problem. According to > http://lwn.net/Articles/627419/ these kmalloc calls never > fail because they allocate less than a page. I strongly suggest you unlearn that fact. The fix for this is in two parts: 1) Annotate using sched_annotate_sleep() and add a comment: we may spin a few times in low memory situations, but this isn't a high performance path. 2) Handle get_config (and other) failure in some more elegant way. Cheers, Rusty.

...fig nor set_config are expected to fail. > > > > > > AFAIK this is currently not a problem. According to > > > http://lwn.net/Articles/627419/ these kmalloc calls never > > > fail because they allocate less than a page. > > > > I strongly suggest you unlearn that fact. > > The fix for this is in two parts: > > > > 1) Annotate using sched_annotate_sleep() and add a comment: we may spin > > a few times in low memory situations, but this isn't a high > > performance path. > > > > 2) Handle get_config (...