Displaying 10 results from an estimated 10 matches for "blocklayout".
2017 Feb 22
3
[Proposal][RFC] Epilog loop vectorization
...vectorized with large vector factor and has a high possibility of executing scalar iterations.
This require following changes:
1) Costing: Preserve all profitable vector factor.
2) Transform: Create an additional vector loop with next profitable vector factor.
Please refer attached file (BlockLayout.png) for the details about transformed block layout.
Patch is available at: https://reviews.llvm.org/D30247
Regards,
Ashutosh
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20170222/19e2c18d/attachment-0001...
2017 Feb 23
2
[Proposal][RFC] Epilog loop vectorization
...oist (unswitch) these
checks out of inner loops (perhaps because they're inside the trip-count
checks?); I wonder if the proposed block structure will make this
situation better or worse (or have no overall effect).
Thanks again,
Hal
>
> Adam
>
>> Please refer attached file (BlockLayout.png) for the details about
>> transformed block layout.
>> Patch is available at:https://reviews.llvm.org/D30247
>> Regards,
>> Ashutosh
>> <BlockLayout.png>_______________________________________________
>> LLVM Developers mailing list
>> llvm-dev a...
2017 Feb 27
4
[Proposal][RFC] Epilog loop vectorization
...er, we often don't hoist (unswitch) these checks out of inner loops (perhaps because they're inside the trip-count checks?); I wonder if the proposed block structure will make this situation better or worse (or have no overall effect).
Thanks again,
Hal
Adam
Please refer attached file (BlockLayout.png) for the details about transformed block layout.
Patch is available at: https://reviews.llvm.org/D30247
Regards,
Ashutosh
<BlockLayout.png>_______________________________________________
LLVM Developers mailing list
llvm-dev at lists.llvm.org<mailto:llvm-dev at lists.llvm.org>
ht...
2017 Feb 27
2
[Proposal][RFC] Epilog loop vectorization
...ide the trip-count checks?); I wonder if the proposed block structure will make this situation better or worse (or have no overall effect).
>>
>> Thanks again,
>> Hal
>>
>>
>>
>> Adam
>>
>>
>>
>> Please refer attached file (BlockLayout.png) for the details about transformed block layout.
>>
>> Patch is available at: https://reviews.llvm.org/D30247 <https://reviews.llvm.org/D30247>
>>
>> Regards,
>> Ashutosh
>>
>> <BlockLayout.png>_________________________________________...
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
...| 4 +-
fs/jffs2/fs.c | 3 +-
fs/jffs2/readinode.c | 4 +-
fs/libfs.c | 4 +-
fs/locks.c | 6 +-
fs/namei.c | 2 +-
fs/nfs/blocklayout/blocklayout.c | 2 +-
fs/nfs/dir.c | 2 +-
fs/nfs/filelayout/filelayout.c | 2 +-
fs/nfs/flexfilelayout/flexfilelayout.c | 2 +-
fs/nfs/fs_context.c | 22 ++--
fs/nfs/nfs3acl.c...
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
...| 4 +-
fs/jffs2/fs.c | 3 +-
fs/jffs2/readinode.c | 4 +-
fs/libfs.c | 4 +-
fs/locks.c | 6 +-
fs/namei.c | 2 +-
fs/nfs/blocklayout/blocklayout.c | 2 +-
fs/nfs/dir.c | 2 +-
fs/nfs/filelayout/filelayout.c | 2 +-
fs/nfs/flexfilelayout/flexfilelayout.c | 2 +-
fs/nfs/fs_context.c | 22 ++--
fs/nfs/nfs3acl.c...
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
...| 4 +-
fs/jffs2/fs.c | 3 +-
fs/jffs2/readinode.c | 4 +-
fs/libfs.c | 4 +-
fs/locks.c | 6 +-
fs/namei.c | 2 +-
fs/nfs/blocklayout/blocklayout.c | 2 +-
fs/nfs/dir.c | 2 +-
fs/nfs/filelayout/filelayout.c | 2 +-
fs/nfs/flexfilelayout/flexfilelayout.c | 2 +-
fs/nfs/fs_context.c | 22 ++--
fs/nfs/nfs3acl.c...
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
...| 4 +-
fs/jffs2/fs.c | 3 +-
fs/jffs2/readinode.c | 4 +-
fs/libfs.c | 4 +-
fs/locks.c | 6 +-
fs/namei.c | 2 +-
fs/nfs/blocklayout/blocklayout.c | 2 +-
fs/nfs/dir.c | 2 +-
fs/nfs/filelayout/filelayout.c | 2 +-
fs/nfs/flexfilelayout/flexfilelayout.c | 2 +-
fs/nfs/fs_context.c | 22 ++--
fs/nfs/nfs3acl.c...
2020 Mar 11
0
[PATCH -next 000/491] treewide: use fallthrough;
...| 4 +-
fs/jffs2/fs.c | 3 +-
fs/jffs2/readinode.c | 4 +-
fs/libfs.c | 4 +-
fs/locks.c | 6 +-
fs/namei.c | 2 +-
fs/nfs/blocklayout/blocklayout.c | 2 +-
fs/nfs/dir.c | 2 +-
fs/nfs/filelayout/filelayout.c | 2 +-
fs/nfs/flexfilelayout/flexfilelayout.c | 2 +-
fs/nfs/fs_context.c | 22 ++--
fs/nfs/nfs3acl.c...
2018 Oct 24
5
Again NFSv4 and Kerberos at the 'samba way'...
....
Based on what i told above, and if you setup as shown above, it should be on the client:
mount -t nfs4 -o sec=krb5,vers=4.1 vdmpp1.ad.fvg.lnf.it:/users /home
And hureay it works ;-) and if not, mail me again. :-(
Last, if you see in you logs.
lkmapd[304]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory
You can ignore this, its known, just wait for the bug fix, its a regresson bug in nfs.
And in reply to the new mail.
You nfs stalled, then it gets mask to prevent other errors.
systemctl unmask nfs-common
systemctl enable nfs-common
If you keep hitting problem...