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

    Greg> No, as Ben said, do not do this.  Use write.  And as you are
    Greg> only doing 1 type of ioctl, it shouldn't be an issue.  Also
    Greg> it will be faster than the ioctl due to lack of BKL usage :)

This is no longer true.  ioctls don't have to take the BKL now that
struct file_operations has unlocked_ioctl and compat_ioctl.

 - R.
-
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: Greg KH <[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]>

• Prev by Date: Re: [RFD] What error should FS return when I/O failure occurs?
• Next by Date: Re: [PATCH] Factor in buddy allocator alignment requirements in node memory alignment
• 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]