What ATA command does read(), write() and dd translate to?
ProgrammingThis forum is for all programming questions.
The question does not have to be directly related to Linux and any language is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
What ATA command does read(), write() and dd translate to?
Hi,
As per the topic, what ATA commands do they translate to? Would a write be translated to WRITE SECTOR, WRITE DMA or WRITE BUFFER or the EXT versions of these commands?
There is no absolute answer to this, since read()s and write()s are a couple of layers removed from the low-level hardware access. Also, it would depend on the filesystem type, since the organization of data on the media (not necessarily an ATA disk) depends on the the filesystem type. The driver for the media would determine the ATA commands employed. You should be able to determine this by looking at the kernel driver source code for the hardware type you use. It may be possible to access the media from user-space using the low-level semantics of the driver, however this would be most unconventional. Applications such as dd operate at the filesystem level, and do not know about the underlying hardware.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.