search for: castig

On Tue, Jan 26, 2016 at 12:10 PM, Paul E. McKenney <paulmck at linux.vnet.ibm.com> wrote: > On Tue, Jan 26, 2016 at 11:44:46AM -0800, Linus Torvalds wrote: >> >> > struct foo *x = READ_ONCE(*ptr); >> > smp_read_barrier_depends(); >> > x->bar = 5; >> >> This case is complete BS. Stop perpetuating it. I already removed

On Tue, Jan 26, 2016 at 12:10 PM, Paul E. McKenney <paulmck at linux.vnet.ibm.com> wrote: > On Tue, Jan 26, 2016 at 11:44:46AM -0800, Linus Torvalds wrote: >> >> > struct foo *x = READ_ONCE(*ptr); >> > smp_read_barrier_depends(); >> > x->bar = 5; >> >> This case is complete BS. Stop perpetuating it. I already removed

...168.1.6 (Email server) from 192.168.0.2 by setting 192.168.0.177 (my linux box's IP on outside LAN). I am beginning to think so far so good. But, Windows networking does not follow suit. I am not able to browse the network when these settings are active. What gives? My guess is I will be castigated for rushing with an email before reading the Archives. But hope springs eternal. Regards, Nandan

...went to the help files and discovered the reason why. My insight as to why it was happening did not immediately provide me with a solution by which I could accomplish what I needed to do. I turned to the help archive. I encountered a thread on which somebody pointed this problem out and was mildly castigated for not having looked at the help file. Alas no workaround was provided. ifelse(test, yes, no) is wonderful since it works well in a dataframe but only if yes and no are something simple, such as a numeric vector. But if yes and no are dates then it does not work. My workaround was quite inel...

...nd > friends. Agreed. We can worry about whether or not we replace the current smp_read_barrier_depends() with that new barrier when and if such hardware appears. > (b) we will have found an architecture with even worse memory > ordering semantics than alpha, and we'll have to stop castigating > alpha for being the worst memory ordering ever. ;-) ;-) ;-) > but I sincerely hope that we'll never find that kind of broken architecture. Apparently at least some hardware vendors are reading memory-barriers.txt, so perhaps the odds of that kind of breakage have reduced....

...nd > friends. Agreed. We can worry about whether or not we replace the current smp_read_barrier_depends() with that new barrier when and if such hardware appears. > (b) we will have found an architecture with even worse memory > ordering semantics than alpha, and we'll have to stop castigating > alpha for being the worst memory ordering ever. ;-) ;-) ;-) > but I sincerely hope that we'll never find that kind of broken architecture. Apparently at least some hardware vendors are reading memory-barriers.txt, so perhaps the odds of that kind of breakage have reduced....

...ier, because "smp_read_barrier_depends()" is not that barrier. We'll presumably then have to make that new barrier part of "rcu_derefence()" and friends. (b) we will have found an architecture with even worse memory ordering semantics than alpha, and we'll have to stop castigating alpha for being the worst memory ordering ever. but I sincerely hope that we'll never find that kind of broken architecture. Linus

...Kanies wrote: > If there were unit tests for documentation sufficiency, I''d feel > pretty differently about it, but there aren''t. I''ve often written > documentation that I thought was sufficient only to have it either > entirely ignored, for who-knows-why, or castigated as being entirely > unrelated to what people want. As someone who compulsively writes documenation, I know exactly what you mean. It seems that no one appreciates the effort invested. But when I look at things from my perspective, I find it so much more rewarding working with software that...

...ad_barrier_depends()" is not that barrier. We'll presumably > then have to make that new barrier part of "rcu_derefence()" and > friends. > > (b) we will have found an architecture with even worse memory > ordering semantics than alpha, and we'll have to stop castigating > alpha for being the worst memory ordering ever. > > but I sincerely hope that we'll never find that kind of broken architecture. So for a moment it looked like MIPS wanted to equal or surpass Alpha in this respect. And Paul made the point that smp_read_barrier_depends() reall...

...ad_barrier_depends()" is not that barrier. We'll presumably > then have to make that new barrier part of "rcu_derefence()" and > friends. > > (b) we will have found an architecture with even worse memory > ordering semantics than alpha, and we'll have to stop castigating > alpha for being the worst memory ordering ever. > > but I sincerely hope that we'll never find that kind of broken architecture. So for a moment it looked like MIPS wanted to equal or surpass Alpha in this respect. And Paul made the point that smp_read_barrier_depends() reall...

...phy* then. The ?science? that lets us spin words until we get ourselves so dizzy we can?t think straight. Sigh. I'm not dizzy, my clarity on this is quite good. Philosophy is in part what's brought us the concept of libre software in the first place, I seriously doubt you're going to castigate the whole concept of free software just because it's founded in a philosophy of, you know, freedom. > > Given that CentOS doesn?t let you create C programs without any knowledge of how to program, would you also argue that CentOS doesn?t give you Freedom 0? No, but that would render...

Hello, There are several important security updates available: Critical: firefox security and bug fix update Important: tomcat5 security update Important: vsftpd security update Moderate: subversion security and bug fix update Important: logwatch security update Important: libtiff security update Moderate: kernel security and bug fix update Important: samba security update Important: samba3x

...but the answer is self-evident in security circles. So instead, I'll ask if this is acceptable in the official CentOS and I can continue to rely on their stuff in their opinion. Again, TIA And, please, no comments on the irony inherent in this. We don't want to be un-subscribed, otherwise castigated or fan the flames of possible list moderation. I know "the powers that be" will appreciate our cooperation. Last TIA -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digi...

I'm receiving the centos-request in digest mode. Using Fedora 10 and Evolution. When I tried to reply to a centos-request message inside the digest, the result doesn't seem to look right. I cut/paste the proper subject line (replacing the CentOS Digest, Vol NN, Issue nn text), but some have complained that this approach doesn't allow the original question and replies to be threaded.

...We can worry about whether or not we replace the current > smp_read_barrier_depends() with that new barrier when and if such > hardware appears. > > > (b) we will have found an architecture with even worse memory > > ordering semantics than alpha, and we'll have to stop castigating > > alpha for being the worst memory ordering ever. > > ;-) ;-) ;-) > > > but I sincerely hope that we'll never find that kind of broken architecture. > > Apparently at least some hardware vendors are reading memory-barriers.txt, > so perhaps the odds of th...

A non-text attachment was scrubbed... Name: not available Type: application/pgp Size: 3562 bytes Desc: not available Url : http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20010214/5489bfec/attachment.bin

On Thu, Jul 2, 2015 at 4:06 PM, Warren Young <wyml at etr-usa.com> wrote: > On Jul 2, 2015, at 9:51 AM, Chris Murphy <lists at colorremedies.com> wrote: >> >>> On 07/01/2015 05:10 PM, Jonathan Billings wrote: >>>> >>>> Nope. CentOS 5, 6 and 7 all support dual-boot. >> >> Considering CentOS 7, at least, doesn't include ntfsprogs,

Dear folks, Here goes my bandwidth manager: INTERNET | |eth0 202.14.41.1 BW.Manager | | | +----eth1----192.168.1.0/24 | +------eth2----192.168.2.0/24 Total incoming bandwidth to eth0 is 1024kbps should be shared to eth1 and eth2, which mean each get 512Kbps and burstable to 1024Kbps if other host is idle. My question is how do i apply HTB to these situation ? As far as i know eth1 and eth2

Hello, I have not had much time to research this problem yet, so please let me know what further information I might be able to provide. This weekend I attempted to upgrade a computer from 8.2-RELEASE-p3 to 8.4 using freebsd-update. After I rebooted to test the new kernel, I got a panic. I had to take a picture of the screen. Here's a condensed version: panic: page fault cpuid = 1 KDB:

Since I had my type development epiphany a couple of days ago, I''ve decided to write down my understanding of developing simple types, at http://reductivelabs.com/trac/puppet/wiki/PracticalTypes. I''d appreciate comments from people who already know how to develop types as to correctness, and also comments from people who are new to type development about whether it''s a