All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Devera <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] squid + tc
Date: Wed, 22 May 2002 18:57:53 +0000	[thread overview]
Message-ID: <marc-lartc-102209391203917@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102205109325878@msgid-missing>

> On Wednesday 22 May 2002 10:43, you wrote:
> > I've seen patch to squid somewhere. The trick is to encode original
> > requester information into new request packets. It can go into
> > "priority" field - it is 32bit and is userspace-settable.
>
> That sounds exactly like the solution I've been looking for for about 3
> months!
>
> Devik, could you possibly find out or give me a hint, where you've seen this
> patch? I am really interested in such a thing and I would be very grateful
> for everything someone knows about it.

I think you should start search at squid page .. but I really
can't remember :(

> > I'm currently thinking about doing something like it but have no
> > time ...
>
> Unfortunataly I currently do not have the time to build it for myself as
> well. (I'm also sure that Devik would be way faster ;)

If someone is willing to spend $1000 I'll write it ;-)

devik

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2002-05-22 18:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-22  7:00 [LARTC] squid + tc Gavin White
2002-05-22  7:27 ` Stef Coene
2002-05-22  8:36 ` Gavin White
2002-05-22  8:43 ` Martin Devera
2002-05-22 17:13 ` Andreas Lehrbaum
2002-05-22 18:35 ` Patrick McHardy
2002-05-22 18:57 ` Martin Devera [this message]
2002-05-23  2:38 ` Patrick McHardy
2002-05-23  7:04 ` Martin Devera
2002-05-23 13:57 ` Patrick McHardy

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=marc-lartc-102209391203917@msgid-missing \
    --to=devik@cdi.cz \
    --cc=lartc@vger.kernel.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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.