search for: backstory

Brief backstory, previous admin is gone and the previous server died. What I could gather was it may have been running Icecast. I setup Icecast on a new CentOS 7 server and the server sits behind a firewall. The links from the users web site points to and internal address for internal users and an link to an ex...

...e: > On May 18, 2020, at 5:13 AM, hw <hw at gc-24.de> wrote: > > > > Is there a better alternative for mounting remote file systems > > over unreliable > > connections? > > I don?t have a good answer for you, because if you?d asked me > without all this backstory whether NFS or SSHFS is more tolerant of > bad connections, I?d have told you SSHFS. On the other hand, NFS is a fully-featured filesystem that supports fancy features like locking and a full ACL system. SSHFS is a FUSE filesystem that will break a lot of software if you try to use it for any...

On Tue, Dec 12, 2017 at 07:55:55PM +0800, Wei Wang wrote: > +int xb_preload_and_set_bit(struct xb *xb, unsigned long bit, gfp_t gfp); I'm struggling to understand when one would use this. The xb_ API requires you to handle your own locking. But specifying GFP flags here implies you can sleep. So ... um ... there's no locking? > +void xb_clear_bit_range(struct xb *xb, unsigned

On Tue, Dec 12, 2017 at 07:55:55PM +0800, Wei Wang wrote: > +int xb_preload_and_set_bit(struct xb *xb, unsigned long bit, gfp_t gfp); I'm struggling to understand when one would use this. The xb_ API requires you to handle your own locking. But specifying GFP flags here implies you can sleep. So ... um ... there's no locking? > +void xb_clear_bit_range(struct xb *xb, unsigned

Hi Sean, > Rafael gave me some of the backstory on this. Basically it is to work around some buggy behavior in the Darwin ar. Adding that on the front of the bitcode file just to get a version doesn't seem > like a very clean thing to do. > > Doug, what other alternatives did you guys consider before settling on this? > > As f...

Hi all, Doug Yung started a discussion earlier ( http://lists.cs.uiuc.edu/pipermail/llvmdev/2014-September/077227.html) about using the unused "version" field in the bitcode wrapper, and I think there was some misunderstanding. I'd like to clarify the motivation. The reason we want to add the version field is to easily identify "old" bitcode. It is only LLVM version

...what I see on the initial review for load combine (https://reviews.llvm.org/D3580) it was not enabled by default because it caused some performance regressions. It's not very surprising, I see how this type of widening can obscure some facts for the rest of the optimizer. I can't find any backstory for this pass, why was it chosen to optimize the pattern in question in this way? What is the current status of this pass? I have an alternative implementation for it locally. I implemented an instcombine rule similar to recognise bswap/bitreverse idiom. It relies on collectBitParts (Local.cpp) to...

...is addressed to a zone managed by that node. Obviously running BIND9_DLZ is more complex than leveraging Samba's built-in DNS server. Why bother with BIND9_DLZ, if it is recommended to run a separate DNS server and forward the AD zone to a DC anyway? What benefit does use BIND9_DLZ provide? Backstory: We used to use Unbound on our pfSense gateway exclusively for DNS. When we provisioned our domain, we pointed clients at the Samba DCs (running the built-in DNS server) for DNS. Samba was configured to forward directly to Google Public DNS, but the latency was poor, as there was no caching on our...

...you have a serious problem > with your system/storage, not with rsync. > > rsync (or the workload) is simply triggering the problem. Thanks for the response . . Hmm . . but the drive that goes read-only is being read FROM not TO . . it is hard to see how that should be an issue? The backstory is that a relatively recent internal 8TB Seagate Barracuda had its 7.2TB sda5 (home) partition corrupted - which itself was suspicious but not impossible of course - so I had to switch temporarily to an external USB 4TB drive (which was a backup drive and was already up-to-date) for /home. So...

Hi, after trying sshfs to mount a remote file system on a server with the result that sshfs will sooner or later get stuck and require a reboot of the client, I'm fed up with it and am looking for alternatives. So next I would like to use NFS over a VPN connection instead. To minimize the instances of the NFS mount getting stuck, it might be helpful to use autofs. What happens when the

...initial review for load combine (https://reviews.llvm.org/D3580) it was not enabled by default because it caused some performance regressions. It's not very surprising, I see how this type of widening can obscure some facts for the rest of the optimizer. >> >> I can't find any backstory for this pass, why was it chosen to optimize the pattern in question in this way? What is the current status of this pass? >> >> I have an alternative implementation for it locally. I implemented an instcombine rule similar to recognise bswap/bitreverse idiom. It relies on collectBitPa...

...or load combine (https://reviews.llvm.org/D3580) it was not enabled by default because it caused some performance regressions. It's not very surprising, I see how this type of widening can obscure some facts for the rest of the optimizer. > >>> > >>> I can't find any backstory for this pass, why was it chosen to optimize the pattern in question in this way? What is the current status of this pass? > >>> > >>> I have an alternative implementation for it locally. I implemented an instcombine rule similar to recognise bswap/bitreverse idiom. It relie...

...( > https://reviews.llvm.org/D3580) it was not enabled by default because it > caused some performance regressions. It's not very surprising, I see how > this type of widening can obscure some facts for the rest of the optimizer. > >>> > >>> I can't find any backstory for this pass, why was it chosen to > optimize the pattern in question in this way? What is the current status of > this pass? > >>> > >>> I have an alternative implementation for it locally. I implemented an > instcombine rule similar to recognise bswap/bitreverse...

...ver locality (for a given RPC, either Foo or Bar gets run). A static >> call graph analysis can provide the needed signals to handle this case >> better. >> >> > Hence you said "allegedly" :) I know we've talked about this before. Just > wanted to put the backstory of the "allegedly" on the list. > Looks like I remembered this wrong. The algorithm in section 3.2 of the paper is call-graph aware. It does do greedy coalescing like a Huffman tree construction algorithms, but constrains the available coalescing operations at each step by call graph...

...eviews.llvm.org/D3580) it was not enabled by default because it >> caused some performance regressions. It's not very surprising, I see how >> this type of widening can obscure some facts for the rest of the optimizer. >> >>> >> >>> I can't find any backstory for this pass, why was it chosen to >> optimize the pattern in question in this way? What is the current status of >> this pass? >> >>> >> >>> I have an alternative implementation for it locally. I implemented an >> instcombine rule similar to recogni...

...dle allocation failure. I think the reason we need xb_preload is because radix tree insertion needs the memory being preallocated already (it couldn't suffer from memory failure during the process of inserting, probably because handling the failure there isn't easy, Matthew may know the backstory of this) So, I think we can handle the memory failure with xb_preload, which stops going into the radix tree APIs, but shouldn't call radix tree APIs without the related memory preallocated. Best, Wei

...think the reason we need xb_preload is because radix tree insertion > > needs the memory being preallocated already (it couldn't suffer from > > memory failure during the process of inserting, probably because > > handling the failure there isn't easy, Matthew may know the backstory > > of > > this) > > According to https://lwn.net/Articles/175432/ , I think that preloading is > needed only when failure to insert an item into a radix tree is a significant > problem. > That is, when failure to insert an item into a radix tree is not a problem, I >...

...eed xb_preload is because radix tree insertion >>>> needs the memory being preallocated already (it couldn't suffer from >>>> memory failure during the process of inserting, probably because >>>> handling the failure there isn't easy, Matthew may know the backstory >>>> of >>>> this) >>> According to https://lwn.net/Articles/175432/ , I think that preloading is >>> needed only when failure to insert an item into a radix tree is a significant >>> problem. >>> That is, when failure to insert an item in...

On May 18, 2020, at 5:13 AM, hw <hw at gc-24.de> wrote: > > Is there a better alternative for mounting remote file systems over unreliable > connections? I don?t have a good answer for you, because if you?d asked me without all this backstory whether NFS or SSHFS is more tolerant of bad connections, I?d have told you SSHFS. NFS comes out of the "Unix lab? world, where all of the computers are hard-wired to nearby servers. It gets really annoyed when packet loss starts happening, and since it?s down in the kernel, that can mean th...

Hello, Just installed 2.1.0, and it seems to be working well. I have a problem I thought user auth on 2.1.0 would fix, namely, I want to control access to an icecast instance which is the source for the primary broadcast icecast. [backstory: a few months ago, the stream was originally broadcasting directly from a box in the engineering room, encoding from a booth line. Listeners would connect directly to this box to listen. After a month broadcasting with this arrangement it became apparent that we were using too much of the ove...