From: Vladislav Bolkhovitin <vst@vlnb.net>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-mm@kvack.org, Christoph Hellwig <hch@infradead.org>,
James Bottomley <James.Bottomley@HansenPartnership.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
scst-devel@lists.sourceforge.net,
Bart Van Assche <bart.vanassche@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [RFC]: Support for zero-copy TCP transmit of user space data
Date: Fri, 19 Dec 2008 20:57:33 +0300 [thread overview]
Message-ID: <494BE08D.30101@vlnb.net> (raw)
In-Reply-To: <20081219180009.GP25779@one.firstfloor.org>
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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2008-12-19 17:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <494009D7.4020602@vlnb.net>
[not found] ` <494012C4.7090304@vlnb.net>
[not found] ` <20081210214500.GA24212@ioremap.net>
[not found] ` <4941590F.3070705@vlnb.net>
[not found] ` <1229022734.3266.67.camel@localhost.localdomain>
[not found] ` <4942BAB8.4050007@vlnb.net>
[not found] ` <1229110673.3262.94.camel@localhost.localdomain>
[not found] ` <49469ADB.6010709@vlnb.net>
[not found] ` <20081215231801.GA27168@infradead.org>
[not found] ` <4947FA1C.2090509@vlnb.net>
2008-12-18 18:35 ` Vladislav Bolkhovitin
2008-12-18 18:43 ` David M. Lloyd
2008-12-19 17:37 ` Vladislav Bolkhovitin
2008-12-19 19:07 ` Jens Axboe
2008-12-19 19:17 ` Vladislav Bolkhovitin
2008-12-19 19:27 ` Jens Axboe
2008-12-19 21:58 ` Evgeniy Polyakov
2008-12-23 19:11 ` Vladislav Bolkhovitin
2008-12-19 11:27 ` Andi Kleen
2008-12-19 17:38 ` Vladislav Bolkhovitin
2008-12-19 18:00 ` Andi Kleen
2008-12-19 17:57 ` Vladislav Bolkhovitin [this message]
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=494BE08D.30101@vlnb.net \
--to=vst@vlnb.net \
--cc=James.Bottomley@HansenPartnership.com \
--cc=andi@firstfloor.org \
--cc=bart.vanassche@gmail.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-scsi@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=scst-devel@lists.sourceforge.net \
/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