notes wasn't such a horrible and unusable hack, so we
had a chance to annotate commits without having to rewrite history...
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
(set-driver_data,
tags-rqs[i], hctx_idx, i,
Another way would be to ensure that the timeout handler doesn't touch
hw_ctx or tag_sets that aren't fully initialized yet. But I think this
is safer/cleaner.
--
Jens Axboe
--
To unsubscribe from
out
(and it is the saner way to do things). So yes, I'd greatly applaud that.
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, May 30 2013, Rusty Russell wrote:
Jens Axboe ax...@kernel.dk writes:
On Wed, Feb 27 2013, Rusty Russell wrote:
Aurelien Jarno aurel...@aurel32.net writes:
Hi,
I have noticed that virtio-rng only returns zero for kernels = 2.6.33
built with CONFIG_HW_RANDOM=m. This is a bit
, offset_in_page(buf));
}
Looks good to me, in lieu of being able to return an error. Want me to
queue it up?
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
think I've come across this
requirement before, since it was introduced (6 years ago, from a cursory
look at the git logs!).
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
On Thu, Feb 07 2013, Paolo Bonzini wrote:
This is useful in places that recycle the same scatterlist multiple
times, and do not want to incur the cost of sg_init_table every
time in hot paths.
Looks fine to me.
Acked-by: Jens Axboe ax...@kernel.dk
--
Jens Axboe
--
To unsubscribe from
for getting that done!
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
bugs in the past.
Asias, this should be trivial to do, except that blk_rq_map_sg()
potentially maps across bio's as well. The tracking of the prev bio_vec
does not care about cross bio boundaries.
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message
() which should take care of it. I tested growing disk
size of already open disk and it works for me.
Thanks, obviously right. Applied.
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
, and where to
put it).
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
.
That's not going to happen, having that lock in there was a disaster for
small IO on fast devices. It's essentially the limiting factor on
benchmark runs on the RHEL kernels that have it included and enabled...
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm
can't allocate it dynamically off the IO path.
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
alloc all
of these when the non-root groups are setup. Why isn't it done that way
right now?
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
merge this for 3.2?
That is, unless Rusty complains shortly ...
Yep, tentatively added.
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
is unfortunate.
How about we apply this as is and look at cleanups as a next step?
Rusty, any opinion on merging this for 3.2?
I expect merge window will open right after the summit,
I can toss it into for-3.2/drivers, if there's consensus to do that now.
--
Jens Axboe
--
To unsubscribe from
is just doing things rather suboptimally in some places,
and that it would be possible to claim most of that speedup there too.
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http
. Thanks
Johannes.
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
as well, I have been hoping for some more adoption
of this. I have mptsas and mpt2sas patches pending as well.
I have not done enough and fully exhaustive weight analysis, so note me
down for wanting such an analysis on virtio_blk as well.
--
Jens Axboe
--
To unsubscribe from this list: send
the flush approach is really workable. Even just strict
ordering of requests could only be supported on SCSI, and even there the
kernel still lacks proper guarantees on error handling to prevent
reordering there.
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body
the driver (except for structure size)
makes no interpretation of the data. The structure
data is copied wholesale to userspace via a
HDIO_GET_IDENTITY ioctl command (eg: hdparm -i dev).
Added!
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message
,
+ VIRTIO_BLK_ID_BYTES);
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
to do that
_before_ putting the queue reference :-)
--
Jens Axboe
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
23 matches
Mail list logo