From: "Kyungmin Park" <kmpark@infradead.org>
To: "Jared Hulbert" <jaredeh@gmail.com>
Cc: "Alan Cox" <alan@lxorguk.ukuu.org.uk>,
"Chris Friesen" <cfriesen@nortel.com>,
linux-kernel@vger.kernel.org
Subject: Re: solid state drive access and context switching
Date: Thu, 6 Dec 2007 12:51:31 +0900 [thread overview]
Message-ID: <9c9fda240712051951w28aae15dle08279f8cc329e95@mail.gmail.com> (raw)
In-Reply-To: <6934efce0712051401x2b137420hb04f971e1ca2cbf6@mail.gmail.com>
Hi,
On Dec 6, 2007 7:01 AM, Jared Hulbert <jaredeh@gmail.com> wrote:
> > Probably about 1000 clocks but its always going to depend upon the
> > workload and whether any other work can be done usefully.
>
> Yeah. Sounds right, in the microsecond range. Be interesting to see data.
>
> Anybody have ideas on what kind of experiments could confirm this
> estimate is right?
Is it the right place to write synchronously?
Now only concern the SATA.
Thank you,
Kyungmin Park
diff --git a/block/ll_rw_blk.c b/block/ll_rw_blk.c
index 3b927be..cce0618 100644
--- a/block/ll_rw_blk.c
+++ b/block/ll_rw_blk.c
@@ -3221,6 +3221,13 @@ static inline void __generic_make_request(struct bio *bio
if (bio_check_eod(bio, nr_sectors))
goto end_io;
+#if 1
+ /* FIXME simple hack */
+ if (MAJOR(bio->bi_bdev->bd_dev) == 8 && bio_data_dir(bio) == WRITE) {
+ /* WRITE_SYNC */
+ bio->bi_rw |= (1 << BIO_RW_SYNC);
+ }
+#endif
/*
* Resolve the mapping until finished. (drivers are
* still free to implement/resolve their own stacking
next prev parent reply other threads:[~2007-12-06 3:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 23:06 Chris Friesen
2007-12-03 23:06 ` Alan Cox
2007-12-04 17:54 ` Jared Hulbert
2007-12-04 20:35 ` Alan Cox
2007-12-04 21:54 ` Jared Hulbert
2007-12-04 22:45 ` Jörn Engel
2007-12-05 0:03 ` Jared Hulbert
2007-12-04 23:24 ` Alan Cox
2007-12-05 0:08 ` Jared Hulbert
2007-12-05 0:24 ` Alan Cox
2007-12-05 22:01 ` Jared Hulbert
2007-12-06 3:51 ` Kyungmin Park [this message]
2007-12-04 20:46 ` Chris Friesen
2007-12-04 21:38 ` Jared Hulbert
2007-12-04 20:52 ` Jeff Garzik
2007-12-04 21:02 ` Alan Cox
[not found] <fa.4uUCLsuQFjc4FtQYCBYK6kY9TiU@ifi.uio.no>
2007-12-05 1:11 ` Robert Hancock
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9c9fda240712051951w28aae15dle08279f8cc329e95@mail.gmail.com \
--to=kmpark@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cfriesen@nortel.com \
--cc=jaredeh@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®