Displaying 20 results from an estimated 300 matches similar to: "[Job Ad]Alibaba Group is hiring deep learning compiler engineers"
2018 May 04
2
Thank you from the Glow Developers
Hello LLVM community,
We have been working hard on a new domain specific optimizing compiler, and
we
are pleased to announce that we have recently open sourced the project! We
would like to introduce you to Glow, an optimizing compiler for neural
networks!
This new compiler is built on the hard work of this community and we would
like
to thank all of the contributors to the LLVM project. We
2018 May 05
0
Thank you from the Glow Developers
Very cool! The first thing that jumps out to me is how tidy and modular the
code structure is. The code feels very familiar (stylistically,
organizationally, etc.) to me as an LLVM developer.
One thing that wasn't at all clear to me is how this is different/similar
to TensorFlow XLA (previously mentioned on this list). Can you briefly
compare and contrast this with TensorFlow XLA?
-- Sean
2012 Oct 26
2
Interpreting and visualising lme results
Dear R users,
I have used the following function (in blue) aiming to find the linear regression between MOE and XLA and nesting my data by Species. I have obtained the following results (in green).
model4<-lme(MOE~XLA, random = ~ XLA|Species, method="ML")summary(model4)
Linear mixed-effects model fit by maximum likelihood Data: NULL AIC BIC logLik -1.040187 8.78533
2018 Jul 20
2
LLVM Social in China - Hangzhou: July 28, 2018
Hi all,
The 3rd HelloLLVM social in China will happen on July 28, 2018.
The location is at Hangzhou, Zhejiang.
Everyone interested in LLVM related projects is invited to join.
Event details is at https://mp.weixin.qq.com/s/Ruf3Dx3GBW37LnUzbfKfNA
BoF style. Presentations are welcome too :-)
Looking forward to meet you !
--
Best wishes,
Wei Wu (吴伟)
2019 Nov 07
5
[PATCH v2 02/15] mm/mmu_notifier: add an interval tree notifier
On 10/28/19 1:10 PM, Jason Gunthorpe wrote:
...
> include/linux/mmu_notifier.h | 98 +++++++
> mm/Kconfig | 1 +
> mm/mmu_notifier.c | 533 +++++++++++++++++++++++++++++++++--
> 3 files changed, 607 insertions(+), 25 deletions(-)
>
> diff --git a/include/linux/mmu_notifier.h b/include/linux/mmu_notifier.h
> index 12bd603d318ce7..51b92ba013ddce
2018 Jul 20
2
[cfe-dev] LLVM Social in China - Hangzhou: July 28, 2018
FYI they organize this kind of stuff throughout the years in different cities. Not sure about Nanjing but I did see one in Shanghai
Zhang
> 在 2018年7月20日,10:40,Shi, Steven via llvm-dev <llvm-dev at lists.llvm.org> 写道:
>
> Is there similar social party in other Chinese cities? Like Shanghai, Nanjing?
>
> Thanks
> Steven Shi
>
>> -----Original Message-----
2019 Oct 23
2
RFC: On non 8-bit bytes and the target for it
This RFC is to ask whether the community is interested in further
discussion of iN bytes support. Last time the issue was on the agenda in
May and the discussion was triggered by Jesper Antonsson's patches (see
<https://lists.llvm.org/pipermail/llvm-dev/2019-May/132080.html>
https://lists.llvm.org/pipermail/llvm-dev/2019-May/132080.html).
It seems that, while some downstream areas
2017 Dec 15
4
RFC: Exposing TargetTransformInfo factories from TargetMachine
On Fri, Dec 15, 2017 at 5:30 AM, Hal Finkel <hfinkel at anl.gov> wrote:
> Are there reasons why we might not want to do this? Other options we should
> consider?
It does make the TargetMachine -> TargetIRAnalysis path less abstract,
but given that all targets have the same pattern of instantiating a
TargetIRAnalysis with a Function->TargetTransformInfo hook, the
abstraction does
2017 Dec 15
2
RFC: Exposing TargetTransformInfo factories from TargetMachine
Hi all,
I'd like to be able to use TargetTransformInfo to make architecture
specific code generation decisions from the XLA LLVM IR emitter[0].
However, we don't have a great way to do this today --
TargetTransformInfo is wrapped in a TargetIRAnalysis and getting the
TargetTransformInfo out of it requires something like:
FunctionAnalysisManager DummyFAM;
TTI = TIRA.run(F, DummyFAM);
2017 Sep 28
0
after hard reboot, split-brain happened, but nothing showed in gluster voluem heal info command !
On Thu, Sep 28, 2017 at 11:41 AM, Zhou, Cynthia (NSB - CN/Hangzhou) <
cynthia.zhou at nokia-sbell.com> wrote:
> Hi,
>
> Thanks for reply!
>
> I?ve checked [1]. But the problem is that there is nothing shown in
> command ?gluster volume heal <volume-name> info?. So these split-entry
> files could only be detected when app try to visit them.
>
> I can find
2017 Sep 28
1
after hard reboot, split-brain happened, but nothing showed in gluster voluem heal info command !
The version I am using is glusterfs 3.6.9
Best regards,
Cynthia ????
MBB SM HETRAN SW3 MATRIX
Storage
Mobile: +86 (0)18657188311
From: Karthik Subrahmanya [mailto:ksubrahm at redhat.com]
Sent: Thursday, September 28, 2017 2:37 PM
To: Zhou, Cynthia (NSB - CN/Hangzhou) <cynthia.zhou at nokia-sbell.com>
Cc: Gluster-users at gluster.org; gluster-devel at gluster.org
Subject: Re: [Gluster-users]
2005 Feb 02
1
Oplock errors in 2.2.8a
Hi,
We are having connection timeout issues in Excel and Word. Was this an
issue that was resolved in post 3.0 versions? We are running 2.2.8a.
Below is the samba log file and I have attached a netmon output.
Thanks,
Domenic
[2005/01/24 09:13:48, 0] smbd/oplock.c:oplock_break(797)
oplock_break: receive_smb timed out after 30 seconds.
oplock_break failed for file
2017 Sep 28
2
after hard reboot, split-brain happened, but nothing showed in gluster voluem heal info command !
Hi,
Thanks for reply!
I?ve checked [1]. But the problem is that there is nothing shown in command ?gluster volume heal <volume-name> info?. So these split-entry files could only be detected when app try to visit them.
I can find gfid mismatch for those in-split-brain entries from mount log, however, nothing show in shd log, the shd log does not know those split-brain entries. Because there
2019 Nov 07
1
[PATCH v2 02/15] mm/mmu_notifier: add an interval tree notifier
On Wed, Nov 06, 2019 at 04:23:21PM -0800, John Hubbard wrote:
> Nice design, I love the seq foundation! So far, I'm not able to spot anything
> actually wrong with the implementation, sorry about that.
Alas :( I feel there must be a bug in here still, but onwards!
One of the main sad points was it didn't make sense to use the
existing seqlock/seqcount primitives as they have
2019 Nov 07
0
[PATCH v2 02/15] mm/mmu_notifier: add an interval tree notifier
On Wed, Nov 06, 2019 at 04:23:21PM -0800, John Hubbard wrote:
> On 10/28/19 1:10 PM, Jason Gunthorpe wrote:
[...]
> > /**
> > * enum mmu_notifier_event - reason for the mmu notifier callback
> > @@ -32,6 +34,9 @@ struct mmu_notifier_range;
> > * access flags). User should soft dirty the page in the end callback to make
> > * sure that anyone relying on
2019 Nov 07
0
[PATCH v2 02/15] mm/mmu_notifier: add an interval tree notifier
On 11/7/19 12:06 PM, Jason Gunthorpe wrote:
...
>>
>> Also, it is best moved down to be next to the new MNR structs, so that all the
>> MNR stuff is in one group.
>
> I agree with Jerome, this enum is part of the 'struct
> mmu_notifier_range' (ie the description of the invalidation) and it
> doesn't really matter that only these new notifiers can be
2017 Sep 28
0
after hard reboot, split-brain happened, but nothing showed in gluster voluem heal info command !
Hi,
To resolve the gfid split-brain you can follow the steps at [1].
Since we don't have the pending markers set on the files, it is not showing
in the heal info.
To debug this issue, need some more data from you. Could you provide these
things?
1. volume info
2. mount log
3. brick logs
4. shd log
May I also know which version of gluster you are running. From the info you
have provided it
2014 Jun 06
3
Loss of Ethernet adaptor
At ~07:40 (UTC-4:00) this morning our gateway host lost its WAN Ethernet
adaptor. Subsequent to recovery, which required a reboot, the following
entries were find in /var/log/messages:
Jun 6 07:39:50 gway02 kernel: PING_FLOOD: IN=eth0 OUT= MAC=00:25:90:61:74:c0:00
:24:14:2b:f2:80:08:00 SRC=74.205.112.125 DST=216.185.71.33 LEN=64 TOS=0x00 PREC=
0x00 TTL=50 ID=30954 PROTO=ICMP TYPE=8 CODE=0
2002 Dec 05
1
swat not working this time
Hi again, I've just reinstalled RH 7.2 and Samba 2.2.7 for the unpteenth
time.... this time swat is not working !!! I have checked the etc/services
file and swat 901/tcp is in there and I have a text file named swat in
etc/xinetd.d directory containing the following...
service swat
{
port = 901
socket_type = stream
wait = no
user = root
server = /usr/local/samba/bin/swat
log_on_failure
2013 Sep 23
1
xen does not work with amd64 kernel but works with 686
Hello,
I have problems running Xen (from Debian 7, i386 userspace) on Asus P3-AE5
system (M2V-TVM board) with Athlon 64 3000+ CPU (AM2, 1.8GHz).
In short, Xen is not accessible from amd64 Linux kernels but works fine with
686 kernels.
Long version:
xen-system-i386 (4.1.4-3+deb7u1) works fine with linux-image-3.2.0-4-686-pae
xen-system-amd64 (4.1.4-3+deb7u1) works fine with