From: Jens Axboe <axboe@kernel.dk>
To: Hannes Reinecke <hare@suse.de>
Cc: linux-block@vger.kernel.org, Mike Christie <mchristi@redhat.com>,
Hannes Reinecke <hare@suse.com>
Subject: Re: [PATCH][RESEND] block: copy ioprio in __bio_clone_fast()
Date: Mon, 26 Feb 2018 09:06:59 -0700 [thread overview]
Message-ID: <cb0a2196-2ec5-e66e-1fc9-e48d51b2ffb6@kernel.dk> (raw)
In-Reply-To: <20180226132906.108227-1-hare@suse.de>
On 2/26/18 6:29 AM, Hannes Reinecke wrote:
> We need to copy the io priority, too; otherwise the clone will run
> with a different priority than the original one.
What about bio_clone_bioset()?
--
Jens Axboe
prev parent reply other threads:[~2018-02-26 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-26 13:29 [PATCH][RESEND] block: copy ioprio in __bio_clone_fast() Hannes Reinecke
2018-02-26 16:06 ` Jens Axboe [this message]
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=cb0a2196-2ec5-e66e-1fc9-e48d51b2ffb6@kernel.dk \
--to=axboe@kernel.dk \
--cc=hare@suse.com \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=mchristi@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).