Re: [PATCH] Documentation/memory-barriers.txt: various fixes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 5/21/07, Jarek Poplawski <[email protected]> wrote:
On Mon, May 21, 2007 at 03:12:07PM +0100, David Howells wrote:
> Jarek Poplawski <[email protected]> wrote:
>
> > > > -     load will be directed), a data dependency barrier would be required to
> > > > +     load will be directed), the data dependency barrier would be required to
> > >
> > > I think that should be "a".
> >
> > I could only guess (it's a magic to me) - so, if it doesn't matter
> > "A data ..." begins this paragraph...
>
> I see what you mean.  I see it as "a data dependency barrier ..." though.  That
> may be because I wrote the doc, however.  I wonder if "data dependency" should
> be hyphenated to make it clearer.  What do you think?

Better don't ask. Now I'm far less decided, than yesterday.
---

"data-dependency barrier" would be better, assuming you mean a barrier
enforcing a data dependency. If you say "data dependency barrier" you
could also mean a "dependency barrier" implemented as a piece of data,
for instance, like a flag value in a data stream that forces
synchronization with another data stream.

scott
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux