From: jitendra.bhivare@broadcom.com (Jitendra Bhivare)
Subject: Read request exceeding max_hw_sectors_kb
Date: Tue, 26 Jun 2018 16:17:35 +0530 [thread overview]
Message-ID: <719bd24e00a4f9ed70b9d17472febf24@mail.gmail.com> (raw)
In-Reply-To: <20180614145447.GB8129@localhost.localdomain>
> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h index
> bca3a92eb55f..9c57b49a4132 100644
> --- a/include/linux/blkdev.h
> +++ b/include/linux/blkdev.h
> @@ -1118,8 +1118,8 @@ static inline unsigned int
blk_max_size_offset(struct
> request_queue *q,
> if (!q->limits.chunk_sectors)
> return q->limits.max_sectors;
>
> - return q->limits.chunk_sectors -
> - (offset & (q->limits.chunk_sectors - 1));
> + return min(q->limits.max_sectors, (unsigned
int)(q->limits.chunk_sectors
> -
> + (offset & (q->limits.chunk_sectors - 1))));
> }
>
> static inline unsigned int blk_rq_get_max_sectors(struct request *rq,
> --
Sorry for the delayed response. This patch works fine too. Please submit
it.
Regards,
JB
WARNING: multiple messages have this Message-ID (diff)
From: Jitendra Bhivare <jitendra.bhivare at broadcom.com>
To: spdk@lists.01.org
Subject: Re: [SPDK] Read request exceeding max_hw_sectors_kb
Date: Tue, 26 Jun 2018 16:17:35 +0530 [thread overview]
Message-ID: <719bd24e00a4f9ed70b9d17472febf24@mail.gmail.com> (raw)
In-Reply-To: 20180614145447.GB8129@localhost.localdomain
[-- Attachment #1: Type: text/plain, Size: 756 bytes --]
> diff --git a/include/linux/blkdev.h b/include/linux/blkdev.h index
> bca3a92eb55f..9c57b49a4132 100644
> --- a/include/linux/blkdev.h
> +++ b/include/linux/blkdev.h
> @@ -1118,8 +1118,8 @@ static inline unsigned int
blk_max_size_offset(struct
> request_queue *q,
> if (!q->limits.chunk_sectors)
> return q->limits.max_sectors;
>
> - return q->limits.chunk_sectors -
> - (offset & (q->limits.chunk_sectors - 1));
> + return min(q->limits.max_sectors, (unsigned
int)(q->limits.chunk_sectors
> -
> + (offset & (q->limits.chunk_sectors - 1))));
> }
>
> static inline unsigned int blk_rq_get_max_sectors(struct request *rq,
> --
Sorry for the delayed response. This patch works fine too. Please submit
it.
Regards,
JB
next prev parent reply other threads:[~2018-06-26 10:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 10:41 Read request exceeding max_hw_sectors_kb Jitendra Bhivare
2018-06-13 10:41 ` [SPDK] " Jitendra Bhivare
2018-06-13 11:47 ` Christoph Hellwig
2018-06-13 11:47 ` [SPDK] " Christoph Hellwig
2018-06-13 17:00 ` Daniel Verkamp
2018-06-13 17:00 ` [SPDK] " Daniel Verkamp
2018-06-14 10:16 ` Jitendra Bhivare
2018-06-14 10:16 ` [SPDK] " Jitendra Bhivare
2018-06-14 14:54 ` Keith Busch
2018-06-14 14:54 ` [SPDK] " Keith Busch
2018-06-15 13:58 ` Jitendra Bhivare
2018-06-15 13:58 ` [SPDK] " Jitendra Bhivare
2018-06-26 10:47 ` Jitendra Bhivare [this message]
2018-06-26 10:47 ` Jitendra Bhivare
2018-06-26 15:07 ` Keith Busch
2018-06-26 15:07 ` [SPDK] " Keith Busch
2018-06-27 10:28 ` Jitendra Bhivare
2018-06-27 10:28 ` [SPDK] " Jitendra Bhivare
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=719bd24e00a4f9ed70b9d17472febf24@mail.gmail.com \
--to=jitendra.bhivare@broadcom.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.