search for: castigating

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

Hi, I am trying to have some routing done between two subnets. One is 192.168.1.0/24 and has my LAN computers running a mix of Windows 98/XP clients. There are two linux machines on this network running Samba. Another is 192.168.0.0/24 and has the other LAN. Only my linux machines have two NICs, one for each LAN. I am trying out one of these linux machines to be the gateway for both the

I encountered the above problem. I 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

...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. Th...

...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. Th...

...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

served by the Type Reference and Function Reference documents, and found the Language Tutorial to be a handy introduction. If I were to ask for more, it would be a Language Reference, and a comprehensive index, because I find search tools generally lacking. On Mon, Aug 27, 2007 at 10:24:04AM -0500, Luke Kanies wrote: > If there were unit tests for documentation sufficiency, I''d feel

...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() really sho...

...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() really sho...

On Thu, Jul 2, 2015 at 5:39 PM, Warren Young <wyml at etr-usa.com> wrote: > On Jul 2, 2015, at 5:14 PM, Chris Murphy <lists at colorremedies.com> wrote: >> >> I've suggested that the distribution doesn't support dual boot if it >> has no hand in making it possible. The user doing this on their own >> manually is user enabled and supported. The distro

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

Two things have been weighing on my mind regarding security issues. The first is that when I downloaded the CentOS 4.1 ISO images, I could not get the sums to match even using different downloads from different mirrors. I decided that that I was doing something wrong and decided to trust the images. So far no regrets. But I am concerned that I get it right the next time. I thought I had read

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 that ki...

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