[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <494BE08D.30101@vlnb.net>
Date: Fri, 19 Dec 2008 20:57:33 +0300
From: Vladislav Bolkhovitin <vst@...b.net>
To: Andi Kleen <andi@...stfloor.org>
CC: linux-mm@...ck.org, Christoph Hellwig <hch@...radead.org>,
James Bottomley <James.Bottomley@...senPartnership.com>,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
scst-devel@...ts.sourceforge.net,
Bart Van Assche <bart.vanassche@...il.com>,
netdev@...r.kernel.org
Subject: Re: [RFC]: Support for zero-copy TCP transmit of user space data
Andi Kleen, on 12/19/2008 09:00 PM wrote:
>> Sure, this is why I propose to disable that option by default in
>> distribution kernels, so it would produce no harm.
>
> That would make the option useless for most users. You might as well
> not bother merging then.
I believe 99.(9)% of users prefer don't patch kernel, if possible.
>> first, only then enable that option, then rebuild the kernel. (I'm
>> repeating it to make sure you didn't miss this my point; it was in the
>> part of my original message, which you cut out.)
>
> That was such a ridiculous suggestion, I didn't take it seriously.
>
> Also it should be really not rocket science to use a separate
> table for this.
Sorry, what do you mean? If usage of something like a hash table to map
pages to the corresponding iSCSI commands, this approach was evaluated
and rejected, because it wouldn't provide much performance increase,
which would worth the effort. See details in the end of the patch
description in http://lkml.org/lkml/2008/12/10/296
Thanks,
Vlad
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists