Hey Thomas thanks for making that clear to me as well. I think you got it right ! On Mon, Jul 28, 2008 at 10:45 AM, Thomas Petazzoni <thomas.petazzoni@xxxxxxxxxxxxxxxxxx> wrote: > Hi, > > Le Sun, 27 Jul 2008 19:45:21 +0530, > "Sandeep K Sinha" <sandeepksinha@xxxxxxxxx> a écrit : > >> The Issue that you discussed is clearly related to barriers, which are >> used extensively in the linux kernel at most of the places as one of >> the synchronization primitive. >> I would suggest you reading more on read/write barriers. >> You found find good explanation on the same in Linux Kernel >> development by Rovert Love. > > I think you are making a confusion here between CPU/compiler barriers > and I/O barriers. What you are talking about are CPU/compiler barriers, > as described in Documentation/memory-barriers.txt. However, Paulo was > probably referring to I/O barriers, as described in > Documentation/block/barrier.txt. > > However, I'm not sure I understand Paulo's request properly. Issuing an > I/O barrier is simply a matter of issuing a bio structure with the > BIO_RW_BARRIER flag set in the bi_rw field of the bio structure. > > Sincerly, > > Thomas > -- > Thomas Petazzoni, Free Electrons > Kernel, drivers and embedded Linux development, > consulting, training and support. > http://free-electrons.com > -- Regards, Sandeep. "To learn is to change. Education is a process that changes the learner." -- To unsubscribe from this list: send an email with "unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx Please read the FAQ at http://kernelnewbies.org/FAQ
