Re: [PATCH 5/7] libata: move and reduce locking to the pio data xfer functions

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

 



> > I'd say this is a non-starter. It solves nothing and means PIO in libata
> > is still basically unusable.
> 
> It doesn't solve the problem completely but still helps, FWIW.  I was

Most transfers for PIO are a single 512 byte transfer per command.

> hoping we could lock only for the last transfer (word).  Would it
> complicate ->data_xfer() too much?

I don't think so. We need to complicate it far more to add 32bit
transfers. We also only have a few ->data_xfer implementations so its
easy to propogate the chance.

Why do we need the lock on the last word transferred anyway. I'm missing
a detail here ?
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Filesystems]     [Linux SCSI]     [Linux RAID]     [Git]     [Kernel Newbies]     [Linux Newbie]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Samba]     [Device Mapper]

  Powered by Linux