Re: [PATCH 7/8] ppc64: SPU file system

> Using a write call instead of read makes the interface even more
> complicated because it would require the user to read the status
> from a separate file after write returns to check what needs to
> be done and then use lseek() or yet another file to access the
> instruction pointer.

Why not just write(pc) to start and read back status from the same
file ?

Ben.


-
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/

---

• Follow-Ups:
  • Re: [PATCH 7/8] ppc64: SPU file system
    • From: Arnd Bergmann <[email protected]>

• References:
  • [PATCH 0/8] ppc64: Introduce Cell/BPA platform, v2
    • From: Arnd Bergmann <[email protected]>
  • [PATCH 7/8] ppc64: SPU file system
    • From: Arnd Bergmann <[email protected]>
  • Re: [PATCH 7/8] ppc64: SPU file system
    • From: Greg KH <[email protected]>
  • Re: [PATCH 7/8] ppc64: SPU file system
    • From: Arnd Bergmann <[email protected]>

• Prev by Date: Re: Mercurial 0.4e vs git network pull
• Next by Date: Re: Automatic .config generation
• Previous by thread: Re: [PATCH 7/8] ppc64: SPU file system
• Next by thread: Re: [PATCH 7/8] ppc64: SPU file system
• Index(es):
  • Date
  • Thread

[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]