Re: [PATCH] block: fix q->max_segment_size checking in blk_recalc_rq_segments about VMERGE

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Mikulas Patocka <mpatocka@...>
Cc: FUJITA Tomonori <fujita.tomonori@...>, <jens.axboe@...>, <linux-kernel@...>, <linux-scsi@...>, <davem@...>, <linux-parisc@...>
Date: Tuesday, July 15, 2008 - 12:36 pm

On Tue, 2008-07-15 at 12:20 -0400, Mikulas Patocka wrote:

It can, but it's not optimal ... and depends on max_phys_segments ==
max_hw_segments.


That's not really a good reason.  You can eliminate code because it's
unused and unikely to be used or you redo it to better or fix it to be
less buggy.  You don't simply eliminate useful functionality that
currently has in-tree users, however marginal you might opine those
users to be.

James


--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH] block: fix q->max_segment_size checking in bl..., James Bottomley, (Tue Jul 15, 12:36 pm)
Re: [PATCH] block: fix q-&gt;max_segment_size checking in bl..., John David Anglin, (Thu Jul 24, 10:40 pm)