|
|
|
|
|
|
|
|
|
|
xen-devel
[Xen-devel] de-BKLing blkfront
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
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
<Prev in Thread] |
Current Thread |
[Next in Thread>
|
- [Xen-devel] de-BKLing blkfront,
Jeremy Fitzhardinge <=
|
|
|
|
|