Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
Subject: Re: Fwd: [PATCH] preliminary implementation of "smart_nopush"
Date: Sat, 29 Jan 2011 04:30:38 +0000	[thread overview]
Message-ID: <20110129043038.GA881@dcvr.yhbt.net> (raw)
In-Reply-To: <20110128093345.GB24894-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>

Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org> wrote:
> > I also wonder if just doing an LD_PRELOAD would be alright or even
> > better since it could track more calls.  Ideally it'd be an option in
> > the kernel (TCP_CORK_LIGHTLY?).  Maybe having an LD_PRELOAD would be a
> > good proof-of-concept for a kernel patch...
> 
> Then I found this:
>   git://git.kernel.org/pub/scm/linux/kernel/git/acme/libautocork
> 
> It's client-oriented at the moment and will need a few patches before
> it's suitable for use with TCP servers, but I've just emailed the author
> about the changes...

I started working on some patches for libautocork here at the moment
  http://bogomips.org/libautocork.git

If we can prove it works for more cases, I'll push for it to become a
kernel option that is fire-and-forget on the listen socket so
applications won't have to keep track of when to cork/uncork sockets
anymore.

I'll probably revert the change to kgio since kgio can't track close()
(nor SSL_read/SSL_write afaik if/when kgio gets SSL support)...

I will do some live testing once I get rid of the hard-coded descriptor
limit and make it thread-safe.

-- 
Eric Wong
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


      parent reply	other threads:[~2011-01-29  4:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28  3:51 Fwd: [PATCH] preliminary implementation of "smart_nopush" Eric Wong
     [not found] ` <20110128035142.GB10919-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2011-01-28  7:18   ` Eric Wong
     [not found]     ` <20110128071831.GA3265-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2011-01-28  9:33       ` Eric Wong
     [not found]         ` <20110128093345.GB24894-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2011-01-29  4:30           ` Eric Wong [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

  List information: https://yhbt.net/rainbows/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110129043038.GA881@dcvr.yhbt.net \
    --to=normalperson-rmlxzr9ms24@public.gmane.org \
    --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org \
    /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. 
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/rainbows.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).