On Tue, Feb 19 2008, Kyungmin Park wrote:
> > >
> > > Agree, however see the following sequence.
> > >
> > > __generic_make_request call q->make_request_fn(q, bio);
> > > It was set by blk_init_queue_node with __make_request.
> > > There are two ways in __make_request.
> > > Case 1, get_rq
> > > Ca
> >
> > Agree, however see the following sequence.
> >
> > __generic_make_request call q->make_request_fn(q, bio);
> > It was set by blk_init_queue_node with __make_request.
> > There are two ways in __make_request.
> > Case 1, get_rq
> > Case 2, out or merged (otherwise you mean unplug case)
> >
>
On Tue, Feb 19 2008, Kyungmin Park wrote:
> > Le Tue, 19 Feb 2008 14:48:18 +0900,
> > "Kyungmin Park" <[EMAIL PROTECTED]> a écrit :
> >
> > > + /* Write synchronous */
> > > + bio->bi_rw |= (1 << BIO_RW_SYNC);
> >
> > Adding BIO_RW_SYNC doesn't make generic_make_reques
> Le Tue, 19 Feb 2008 14:48:18 +0900,
> "Kyungmin Park" <[EMAIL PROTECTED]> a écrit :
>
> > + /* Write synchronous */
> > + bio->bi_rw |= (1 << BIO_RW_SYNC);
>
> Adding BIO_RW_SYNC doesn't make generic_make_request() synchronous as
> in "generic_make_request() returns
Hi,
Le Tue, 19 Feb 2008 14:48:18 +0900,
"Kyungmin Park" <[EMAIL PROTECTED]> a écrit :
> + /* Write synchronous */
> + bio->bi_rw |= (1 << BIO_RW_SYNC);
Adding BIO_RW_SYNC doesn't make generic_make_request() synchronous as
in "generic_make_request() returns only after
Hi,
Don't you remember the topic "solid state drive access and context
switching" [1].
I want to measure it is really better performance on SSD?
To write it on ssd synchronously, I hacked the
'generic_make_request()' [2] and got following results.
# echo 3 > /proc/sys/vm/drop_caches
# tiotest -f
