Re: Software Pipelining

"Christopher Glaeser" <cdg@nullstone.com>
Sun, 21 Sep 2008 23:47:16 -0700

          From comp.compilers
Related articles
[5 earlier articles]
Re: Software Pipelining sidtouati@inria.fr (Touati Sid) (2008-09-08)
Re: Software Pipelining kamalpr@hp.com (kamal) (2008-09-10)
Re: Software Pipelining johnhull2008@gmail.com (johnhull2008) (2008-09-11)
Re: Software Pipelining plfriko@yahoo.de (Tim Frink) (2008-09-16)
Re: Software Pipelining plfriko@yahoo.de (Tim Frink) (2008-09-16)
Re: Software Pipelining pertti.kellomaki@tut.fi (Pertti Kellomaki) (2008-09-17)
Re: Software Pipelining cdg@nullstone.com (Christopher Glaeser) (2008-09-21)
Re: Software Pipelining armelasselin@hotmail.com (Armel) (2008-09-24)
Software pipelining napi@rangkom.MY (1991-07-04)
Re: Software pipelining pardo@gar.cs.washington.edu (1991-07-19)
| List of all articles for this month |
From: "Christopher Glaeser" <cdg@nullstone.com>
Newsgroups: comp.compilers
Date: Sun, 21 Sep 2008 23:47:16 -0700
Organization: Compilers Central
References: 08-08-072 08-08-086 08-08-092 08-09-060 08-09-079
Keywords: optimize
Posted-Date: 23 Sep 2008 14:12:33 EDT

> Even though I understand that this is an example, I still have the
> feeling that with just a single functional unit, the benefits of
> pipelining are marginal,


Actually, the benefits of software pipelining can be significant, even
for a single functional unit, if that functional unit has a multistage
pipeline. Assuming the number of iterations is sufficiently large to
mask the prologue and epiloque, the number of cycles required to
execute any given iteration doesn't really matter. The key is to
minimize the number of cycles needed to start each successive
iteration, otherwise known as the minimum iteration interval (MII).


Best,
Christopher Glaeser


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.