All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Daniel Stodden <daniel.stodden@citrix.com>
Cc: "Xen-devel@lists.xensource.com" <Xen-devel@lists.xensource.com>
Subject: de-BKLing blkfront
Date: Wed, 21 Jul 2010 12:49:49 -0700	[thread overview]
Message-ID: <4C474F5D.80204@goop.org> (raw)

When I was preparing the latest set of blkfront patches to send upstream
to Jens Axboe, he pointed out there were conflicts with what he
currently has queued.

It turns out the conflict was from pushing the BKL (lock/unlock_kernel)
into the open and release functions.  I did the merge keeping them
around all the new stuff you added to those functions, but I wonder if
its actually necessary.  Do we rely on open/release being globally
serialized in there?

I've pushed what I have into the upstream/blkfront branch in xen.git.

Thanks,
    J

             reply	other threads:[~2010-07-21 19:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-21 19:49 Jeremy Fitzhardinge [this message]
2010-07-21 21:12 ` de-BKLing blkfront Daniel Stodden
2010-07-21 21:39   ` Jeremy Fitzhardinge
2010-07-21 22:26     ` Daniel Stodden
2010-07-21 23:32       ` Jeremy Fitzhardinge

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=4C474F5D.80204@goop.org \
    --to=jeremy@goop.org \
    --cc=Xen-devel@lists.xensource.com \
    --cc=daniel.stodden@citrix.com \
    /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.