Re: [PATCH 026 of 35] Split any large bios that arrive at __make_request.

2007-08-01 Thread Neil Brown
On Thursday August 2, [EMAIL PROTECTED] wrote: > Neil Brown wrote: > > > > If you confirm that 027 isn't applying, I'll track down what happened. > > You're right. I don't have patch 27. Looking Ummm... It's not in > my LKML folder either. Can you resend it? > > Thanks. > > -- > tejun

Re: [PATCH 026 of 35] Split any large bios that arrive at __make_request.

2007-08-01 Thread Tejun Heo
Neil Brown wrote: > On Thursday August 2, [EMAIL PROTECTED] wrote: >> Hmmm... Patches don't apply beyond this one. I'm applying against >> clean 2.6.23-rc1-mm1 grabbed using ketchup. >> > > So do you mean 027 doesn't apply, or that 028 doesn't apply next? > > It is possible that you missed 027.

Re: [PATCH 026 of 35] Split any large bios that arrive at __make_request.

2007-08-01 Thread Neil Brown
On Thursday August 2, [EMAIL PROTECTED] wrote: > Hmmm... Patches don't apply beyond this one. I'm applying against > clean 2.6.23-rc1-mm1 grabbed using ketchup. > So do you mean 027 doesn't apply, or that 028 doesn't apply next? It is possible that you missed 027. It originally has 3 consecuti

Re: [PATCH 026 of 35] Split any large bios that arrive at __make_request.

2007-08-01 Thread Tejun Heo
Hmmm... Patches don't apply beyond this one. I'm applying against clean 2.6.23-rc1-mm1 grabbed using ketchup. -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-

[PATCH 026 of 35] Split any large bios that arrive at __make_request.

2007-07-30 Thread NeilBrown
Now that bi_io_vec and bio can be shared, we can handle arbitrarily large bios in __make_request by splitting them over multiple requests. If we do split a request, we mark both halves as "REQ_NOMERGE". It is only really necessary to mark the first part as NO_BACK_MERGE and the second part as NO