mbs-octoml commented on pull request #38:
URL: https://github.com/apache/tvm-rfcs/pull/38#issuecomment-932274086
Thanks @manupa-arm for the reminder there were some good comments on #8892.
I see a work stream:
1. get the multi-target handling under control, and stop relying on the
limiting device type -> target mapping
2. allow device planning to be re-run with additional memory scope
constraints to further partition, those constraints may originate in already
lowered PrimFuncs.
3. allow labeling of sets of target/devices a la BYOC target labeling (but
probably continue to just pick the 'first')
4. bring BYOC target labeling / partitioning and device planning together
5. replace naive partitioning with something subject to optimization
Here I want to just focus on 1 -- everything beyond that really needs
face-to-face discussion.
From 2 onward obviously overlaps your USMP. My vague thought was we can work
from opposite ends and reconcile at 5. Ie 2-4 sets us up to work in a combined
Relay+TIR world, then 5 is where everything we've learned from USMP could
perhaps be replayed. Anyway, that's just a vague thought so I'd love to talk
more about it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
