tpb has joined #litex
Dolu has joined #litex
freemint has joined #litex
freemint has quit [Client Quit]
_whitelogger has joined #litex
_whitelogger has joined #litex
rohitksingh has quit [Ping timeout: 245 seconds]
CarlFK has joined #litex
nrossi has joined #litex
CarlFK has quit [Read error: Connection reset by peer]
rohitksingh has joined #litex
ambro718 has joined #litex
ambro718 has quit [Ping timeout: 252 seconds]
rohitksingh has quit [Ping timeout: 250 seconds]
<somlo> _florent_, daveshah: tried the point-to-point 128-wide rocket<->litedram link with LiteDRAMAXI2Native buffer_depth as low as 2 (for both write and read), still won't fit on the versa5g (got an assert error when I tried buffer_depth = 1 :)
<somlo> this is just fyi, not actually asking for anything right now :)
<daveshah> Thanks for testing!
<_florent_> somlo: ok, maybe you can also test by changing buffered=True to buffered=False on w_buffer/r_buffer
<somlo> _florent_: 99%, now placing and routing, after which I'll try to start it up :)
<somlo> I'll have to use the trellisboard to measure if (and how much) removing buffering affects performance
<somlo> but my hunch is not much (if at all), since this is a point-to-point connection
<somlo> and it boots, and works fine, seems to have decent performance as well
<somlo> now, back to the trellisboard, where I can verify whether reduced buffering has any sort of impact on performance, before we decide if it's worth talking about exposing the true/false option through a LiteDRAMAXI2Native parameter...
<_florent_> somlo: ok good. The current w/r_buffer depth were a good compromise (resource usage vs performance) i found while testing LiteDRAM on DDR4 with continuous writes/reads, but that's possible it's not optimal for your use-case, so this could indeed be interesting to expose more parameters.
<somlo> didn't have patience to wait for nbench memory-specific results, but the integer tests feel marginally better on the original (unmodified) buffer depth
<somlo> so we'd only do it for area, and that also only for the versa, and only with the current state of nextpnr :)
<somlo> I'd say it isn't worth it, I'd rather wait for daveshah's next round of p&r improvements :)
<somlo> particularly since I'm now focusing on the trellisboard, which has sufficient room to spare
<somlo> in the mean time, litex+rocket fits fine on the versa when using the wishbone-based width converter, so it's not like one can't get a bitstream to boot 64bit linux if they really really want it...
CarlFK has joined #litex
CarlFK has quit [Quit: Leaving.]
Dolu has quit [Ping timeout: 265 seconds]
ambro718 has joined #litex
CarlFK has joined #litex
rohitksingh has joined #litex
rohitksingh has quit [Ping timeout: 240 seconds]
rohitksingh has joined #litex
rohitksingh has quit [Ping timeout: 265 seconds]
nrossi has quit [Quit: Connection closed for inactivity]
Dolu has joined #litex
freemint has joined #litex
freemint has quit [Remote host closed the connection]
freemint has joined #litex
tpb has quit [Remote host closed the connection]