All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff Dike <jdike@addtoit.com>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net,
	Bodo Stroesser <bstroesser@fujitsu-siemens.com>
Subject: Re: [uml-devel] Review needed for ubd fixes
Date: Wed, 28 Sep 2005 11:54:05 -0400	[thread overview]
Message-ID: <20050928155405.GA12888@ccure.user-mode-linux.org> (raw)
In-Reply-To: <200509281414.32622.blaisorblade@yahoo.it>

On Wed, Sep 28, 2005 at 02:14:32PM +0200, Blaisorblade wrote:
> 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).

I think that doesn't matter too much.  I have to get the sg information out
of it, and store that, plus the current position within the sg array if
we couldn't send it all to the host.  So, I don't refer to the request after
I get the sg information out of it, so I might as well remove it from the
queue.

> 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).

Yeah, I wasn't planning on sending that for 2.6.14.  It was just part of that
set of patches.

> 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 thought I did.  AIO had been in my tree forever with no apparent problems.
I recently started running 24 hour/day stress tests on UML, and that turned
up some problems.  People turning on spinlock debugging turned up the sleeping
while atomic problem.  And me staring at the code as a result of that turned
up the possible deadlock.

> 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).

Yeah.  This still needs some work.  I need to deal with the bitmap array
properly.

				Jeff


-------------------------------------------------------
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

  reply	other threads:[~2005-09-28 16:18 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
2005-09-28 15:54                   ` Jeff Dike [this message]
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=20050928155405.GA12888@ccure.user-mode-linux.org \
    --to=jdike@addtoit.com \
    --cc=blaisorblade@yahoo.it \
    --cc=bstroesser@fujitsu-siemens.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.