From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>,
Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [uml-devel] Review needed for ubd fixes
Date: Wed, 28 Sep 2005 14:14:32 +0200 [thread overview]
Message-ID: <200509281414.32622.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050927181218.GA28937@ccure.user-mode-linux.org>
On Tuesday 27 September 2005 20:12, Jeff Dike wrote:
> Attached is my current set of I/O patches. It's significantly different,
> and simpler, than my previous set.
> Now, there is no sleeping while running the queue, so the spinlock is never
> dropped, and all of the extra synchronization is gone.
Very, very nice.
What about the early removal of the request from the queue, before being sure
we can complete it (sorry for not reading carefully everything below, I'm
going to have lunch and afterwards back to study).
> o_direct adds O_DIRECT support to UML and makes the ubd driver use it.
>
> aio-errors makes submit_aio_24 return -errno instead of -1.
Reorder o_direct at the end - no time to read them yet, but guess that more
intrusive goes at the end. And I'm not sure whether merging o_direct so late
in 2.6.14 is nice (even if you've tested the full patch set, and without
o_direct the thing makes less sense).
Let's hope for the better, but next time the debug should be done *before*
merging, ok? Even because, for instance, if (say) the patch was ready for
2.6.14 and merged into 2.6.15, I could have released a test tree against
2.6.14 (maybe I could do this now).
> I've given this a bunch of testing and it has survived overnight kernel
> build loops on both x86 and x86_64.
> The attached patches are against 2.6.14-rc2.
Please, send them to Andrew for -mm, and say "2.6.14 can't go without them,
but they might need further review".
And ask Jens Axboe if it can give a look to them (this time it's less
necessary, since there are less dirty tricks).
> Jeff
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-09-28 12:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-17 22:45 [uml-devel] Review needed for ubd fixes Jeff Dike
2005-09-20 12:01 ` Blaisorblade
2005-09-20 19:06 ` Jeff Dike
2005-09-21 15:49 ` Blaisorblade
2005-09-21 18:04 ` Jeff Dike
2005-09-21 19:06 ` Blaisorblade
2005-09-21 20:45 ` Jeff Dike
2005-09-22 20:51 ` Blaisorblade
2005-09-27 18:12 ` Jeff Dike
2005-09-28 12:14 ` Blaisorblade [this message]
2005-09-28 15:54 ` Jeff Dike
2005-09-28 16:47 ` Blaisorblade
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=200509281414.32622.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=bstroesser@fujitsu-siemens.com \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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