From: gypsy <gypsy@iswest.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] [PATCH] mark in u32
Date: Sat, 08 Jan 2005 04:58:03 +0000 [thread overview]
Message-ID: <41DF685B.2B595FB@iswest.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0501051151270.8614@webhosting.rdsbv.ro>
gypsy wrote:
>
> Thomas Graf wrote:
> >
>
> > Would you guys like to see esfq included in mainline?
>
> YES!!
>
> gypsy
Thomas,
Let me rephrase that.
I can't think of any reason that SFQ should be maintained without the E
<grin>. It makes very little sense to hard code parameters that the
user might wish or need to supply. That's the reason for ESFQ. When no
parameters are given, it _is_ SFQ; when there are parameters it complies
with ones wishes.
Name it what you like, but SFQ desperately needs to accept paramters,
and ESFQ should be the only SFQ.
gypsy
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2005-01-08 4:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 10:05 [LARTC] [PATCH] mark in u32 Catalin(ux aka Dino) BOIE
2005-01-05 14:59 ` Andy Furniss
2005-01-05 15:10 ` Thomas Graf
2005-01-05 15:25 ` Andy Furniss
2005-01-05 15:52 ` Thomas Graf
2005-01-05 16:40 ` Andy Furniss
2005-01-05 23:44 ` Stephen Hemminger
2005-01-06 8:53 ` Andy Furniss
2005-01-06 9:00 ` Andy Furniss
2005-01-06 9:50 ` Thomas Graf
2005-01-06 13:27 ` Andy Furniss
2005-01-06 16:45 ` Thomas Graf
2005-01-06 23:23 ` Andy Furniss
2005-01-06 23:25 ` Thomas Graf
2005-01-06 23:35 ` Andy Furniss
2005-01-07 2:45 ` Andy Furniss
2005-01-07 10:29 ` Andy Furniss
2005-01-08 2:34 ` Andy Furniss
2005-01-08 4:14 ` gypsy
2005-01-08 4:58 ` gypsy [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=41DF685B.2B595FB@iswest.com \
--to=gypsy@iswest.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox