From: Jeff Moyer <jmoyer@redhat.com>
To: Tahsin Erdogan <tahsin@google.com>
Cc: Jens Axboe <axboe@kernel.dk>,
Aaron Carroll <aaronc@gelato.unsw.edu.au>,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] deadline: remove unused struct member
Date: Mon, 01 Feb 2016 10:10:32 -0500 [thread overview]
Message-ID: <x49k2moeaaf.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <CAAeU0aOE_XQ6AwoAcvA3_T=8yWPnXtZJQKGd1y0T1WnB3qwPBw@mail.gmail.com> (Tahsin Erdogan's message of "Sun, 31 Jan 2016 16:54:27 -0800")
Tahsin Erdogan <tahsin@google.com> writes:
> Ping?
Yeah, commit 63de428b139d3 (deadline-iosched: allow non-sequential
batching) removed the use of last_sector, and should have removed the
structure member as well (way back in 2008).
Reviewed-by: Jeff Moyer <jmoyer@redhat.com>
> On Thu, Jan 14, 2016 at 2:41 PM, Tahsin Erdogan <tahsin@google.com> wrote:
>> commit 63de428b139d3d31d86ebe25ae97b33f6540fb7e ("deadline-iosched:
>> allow non-sequential batching") removed last use of last_sector.
>>
>> Signed-off-by: Tahsin Erdogan <tahsin@google.com>
>> ---
>> block/deadline-iosched.c | 3 ---
>> 1 file changed, 3 deletions(-)
>>
>> diff --git a/block/deadline-iosched.c b/block/deadline-iosched.c
>> index a753df2..d0dd788 100644
>> --- a/block/deadline-iosched.c
>> +++ b/block/deadline-iosched.c
>> @@ -39,7 +39,6 @@ struct deadline_data {
>> */
>> struct request *next_rq[2];
>> unsigned int batching; /* number of sequential requests made */
>> - sector_t last_sector; /* head position */
>> unsigned int starved; /* times reads have starved writes */
>>
>> /*
>> @@ -210,8 +209,6 @@ deadline_move_request(struct deadline_data *dd, struct request *rq)
>> dd->next_rq[WRITE] = NULL;
>> dd->next_rq[data_dir] = deadline_latter_request(rq);
>>
>> - dd->last_sector = rq_end_sector(rq);
>> -
>> /*
>> * take it off the sort and fifo list, move
>> * to dispatch queue
>> --
>> 2.6.0.rc2.230.g3dd15c0
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-block" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-02-01 15:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-14 22:41 Tahsin Erdogan
2016-02-01 0:54 ` Tahsin Erdogan
2016-02-01 15:10 ` Jeff Moyer [this message]
2016-02-01 16:10 ` Jens Axboe
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=x49k2moeaaf.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=aaronc@gelato.unsw.edu.au \
--cc=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tahsin@google.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
all inboxes | Powered by JetHome®