Thomas Petazzoni escreveu:
...
Paulo was
probably referring to I/O barriers, as described in
Documentation/block/barrier.txt.
Yes, that's the point ...
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
Thomas Petazzoni escreveu:
...
Paulo was
probably referring to I/O barriers, as described in
Documentation/block/barrier.txt.
Yes, that's the point ...
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
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
<[EMAIL PROTECTED]> wrote:
> Hi,
>
> Le Sun, 27 Jul 2008 19:45:21 +0530,
> "Sandeep K Sinha" <[EMAIL PROTECTED]> a écrit :
>
>> The Issue that you discussed is clea
Hi,
Le Sun, 27 Jul 2008 19:45:21 +0530,
"Sandeep K Sinha" <[EMAIL PROTECTED]> 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 mo
Hey paulo,
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
Hi!
I am learning linkux kernel internals and facing the following problem:
1. I use __bread to read a fixed place block on a block drive.
2. I use submit_bio to read/write data on the same drive. The order the
data is written may be arbitrary and, in general, it almost never occur
at the sam
