Displaying 20 results from an estimated 2000 matches similar to: "[LLVMdev] Coarse-grained parallelism"
2011 Apr 19
0
[LLVMdev] Coarse-grained parallelism
On 4/19/11 5:57 AM, Andreas Wilhelm wrote:
> Hello,
>
> I found some code within the pool allocation project to identify
> parallelizable function calls.
> Unfortunately the functionality isn't part of the current release of
> poolalloc (in release 14 it was).
Can you tell me in what file(s) this is implemented? I wasn't aware
that the poolalloc project had such an
2011 Apr 20
3
[LLVMdev] Coarse-grained parallelism
Am 19.04.2011 um 16:44 schrieb John Criswell:
> On 4/19/11 5:57 AM, Andreas Wilhelm wrote:
>>
>> Hello,
>>
>> I found some code within the pool allocation project to identify parallelizable function calls.
>> Unfortunately the functionality isn't part of the current release of poolalloc (in release 14 it was).
>
> Can you tell me in what file(s) this
2011 Apr 22
0
[LLVMdev] Coarse-grained parallelism
On 04/20/2011 08:05 AM, Andreas Wilhelm wrote:
> Am 19.04.2011 um 16:44 schrieb John Criswell:
>
>> On 4/19/11 5:57 AM, Andreas Wilhelm wrote:
>>> Hello,
>>>
>>> I found some code within the pool allocation project to identify
>>> parallelizable function calls.
>>> Unfortunately the functionality isn't part of the current release of
2011 Apr 27
1
[LLVMdev] Coarse-grained parallelism
Am 22.04.2011 um 18:03 schrieb Tobias Grosser:
> On 04/20/2011 08:05 AM, Andreas Wilhelm wrote:
>> Am 19.04.2011 um 16:44 schrieb John Criswell:
>>
>>> On 4/19/11 5:57 AM, Andreas Wilhelm wrote:
>>>> Hello,
>>>>
>>>> I found some code within the pool allocation project to identify
>>>> parallelizable function calls.
2017 Oct 22
0
[PATCH v1 1/3] virtio-balloon: replace the coarse-grained balloon_lock
On 10/22/2017 01:20 PM, Tetsuo Handa wrote:
> Wei Wang wrote:
>> The balloon_lock was used to synchronize the access demand to elements
>> of struct virtio_balloon and its queue operations (please see commit
>> e22504296d). This prevents the concurrent run of the leak_balloon and
>> fill_balloon functions, thereby resulting in a deadlock issue on OOM:
>>
>>
2017 Oct 22
1
[PATCH v1 1/3] virtio-balloon: replace the coarse-grained balloon_lock
Wei Wang wrote:
> >> @@ -162,20 +160,20 @@ static unsigned fill_balloon(struct virtio_balloon *vb, size_t num)
> >> msleep(200);
> >> break;
> >> }
> >> - set_page_pfns(vb, vb->pfns + vb->num_pfns, page);
> >> - vb->num_pages += VIRTIO_BALLOON_PAGES_PER_PAGE;
> >> + set_page_pfns(vb, pfns + num_pfns, page);
2017 Oct 22
1
[PATCH v1 1/3] virtio-balloon: replace the coarse-grained balloon_lock
Wei Wang wrote:
> >> @@ -162,20 +160,20 @@ static unsigned fill_balloon(struct virtio_balloon *vb, size_t num)
> >> msleep(200);
> >> break;
> >> }
> >> - set_page_pfns(vb, vb->pfns + vb->num_pfns, page);
> >> - vb->num_pages += VIRTIO_BALLOON_PAGES_PER_PAGE;
> >> + set_page_pfns(vb, pfns + num_pfns, page);
2017 Oct 20
0
[PATCH v1 1/3] virtio-balloon: replace the coarse-grained balloon_lock
The balloon_lock was used to synchronize the access demand to elements
of struct virtio_balloon and its queue operations (please see commit
e22504296d). This prevents the concurrent run of the leak_balloon and
fill_balloon functions, thereby resulting in a deadlock issue on OOM:
fill_balloon: take balloon_lock and wait for OOM to get some memory;
oom_notify: release some inflated memory via
2017 Oct 22
2
[PATCH v1 1/3] virtio-balloon: replace the coarse-grained balloon_lock
Wei Wang wrote:
> The balloon_lock was used to synchronize the access demand to elements
> of struct virtio_balloon and its queue operations (please see commit
> e22504296d). This prevents the concurrent run of the leak_balloon and
> fill_balloon functions, thereby resulting in a deadlock issue on OOM:
>
> fill_balloon: take balloon_lock and wait for OOM to get some memory;
>
2017 Oct 22
2
[PATCH v1 1/3] virtio-balloon: replace the coarse-grained balloon_lock
Wei Wang wrote:
> The balloon_lock was used to synchronize the access demand to elements
> of struct virtio_balloon and its queue operations (please see commit
> e22504296d). This prevents the concurrent run of the leak_balloon and
> fill_balloon functions, thereby resulting in a deadlock issue on OOM:
>
> fill_balloon: take balloon_lock and wait for OOM to get some memory;
>
2016 May 23
1
Andersens analysis ?
Hi all,
I was trying to find the equivalent analysis of Andersens on LLVM.
I found it only on LLVM 2.6 on 'Analysis/IPA' folder.
Is it removed/renamed on later versions? I'm mostly interested in 3.4
version or later.
Thank you in advance,
--
Irini
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2012 Oct 30
1
[LLVMdev] Program Dependence Graph (PDG) in LLVM
Hi,
Is there a way to use LLVM to build the visual representation of program
dependence graph (PDG) of a routine/program?
>From looking at
https://llvm.org/svn/llvm-project/poolalloc/branches/release_14/lib/DSA/PgmDependenceGraph.cpp,
it looks like there is an incomplete implementation of PDG in LLVM.
However, when I search within LLVM3.0 package, I don't find the .cpp/h
code. So, I also
2017 Jan 03
2
Automatic Insertion of OpenACC/OpenMP directives
> On Jan 3, 2017, at 7:17 AM, Jonathan Roelofs <jonathan at codesourcery.com> wrote:
>
>
>
> On 12/31/16 12:37 PM, Fernando Magno Quintao Pereira via llvm-dev wrote:
>> Dear Mehdi,
>>
>> I've changed your example a little bit:
>>
>> float saxpy(float a, float *x, float *y, int n) {
>> int j = 0;
>> for (int i = 0; i < n;
2020 Aug 24
4
smbclient mask command seems not to work the same way with recurse ON for mget and mput
A new update. Same behaviour with 4.6.16. Exact issue as Bug 1249.
Many thanks. Kind regards.
El lun., 24 ago. 2020 a las 12:23, LPC DPG (<lpcdpg at gmail.com>) escribi?:
> Dear folks.
>
> Was hoping it had to do with the release, but have also tested in 4.4.16
> and the issue is also there. I am aware a RHEL/CEntOS based upon 6
> distribution is not the most up to date
2016 Nov 23
3
LLD: time to enable --threads by default
Interesting. Might be worth giving a try again to the idea of creating
the file in anonymous memory and using a write to output it.
Cheers,
Rafael
On 23 November 2016 at 02:41, Sean Silva via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
>
>
> On Wed, Nov 16, 2016 at 12:44 PM, Rui Ueyama via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>>
>> LLD supports
2020 Aug 25
2
smbclient mask command seems not to work the same way with recurse ON for mget and mput
Dear Andrew.
You are right, I should have taken a deeper look into the standard output
during compilation. I did just assume source4 was the one for Samba4.
Anyway, besides the source confusion (really, even if I had found the right
one, following the code would have been out of my reach), I don't seem to
find how that is related with the documentation issue, or the
mput/mask/recurse
2016 Nov 16
9
LLD: time to enable --threads by default
LLD supports multi-threading, and it seems to be working well as you can
see in a recent result
<http://llvm.org/viewvc/llvm-project?view=revision&revision=287140>. In
short, LLD runs 30% faster with --threads option and more than 50% faster
if you are using --build-id (your mileage may vary depending on your
computer). However, I don't think most users even don't know about that
2020 Aug 25
1
smbclient mask command seems not to work the same way with recurse ON for mget and mput
Dear all.
I would like to propose a possible way to make mget and mput behave more or
less the same way, rather that just changing documentation. Please, bear in
mind this is a poor attempt coming from a person with no C skills at all,
so other than testing that only filtered files are transferred, I have not
gone further. Hope at least to have been able not to corrupt any pointer,
but I'm
2004 Jan 08
1
[LLVMdev] Re: idea 10
Hello Valery,
I have some comments regarding your thoughts on LLVM support for
distributed computing.
Valery A.Khamenya wrote:
>There should be an engine and layer for making dispatching optimizations in run-time. If one CPU is loaded and code is
>"parallelizable" why then not to send some part of
>calculation to other CPU? This kind of on-fly decision will
>be one day
2019 Feb 15
2
Can we disable diffie-hellman-group-exchange-sha1 by default?
On Fri, 2019-02-15 at 15:57 +1100, Darren Tucker wrote:
> That was the original intent (and it's mentioned in RFC4419) however
> each moduli file we ship (70-80 instances of 6 sizes) takes about 1
> cpu-month to generate on a lowish-power x86-64 machine. Most of it
> is
> parallelizable, but even then it'd likely take a few hours to
> generate
> one of each size. I