From: bert hubert <ahu@ds9a.nl>
To: Ben Greear <greearb@candelatech.com>
Cc: davids@webmaster.com, linux-kernel@vger.kernel.org
Subject: Re: Select/Poll
Date: Wed, 2 Jun 2004 08:38:03 +0200 [thread overview]
Message-ID: <20040602063803.GA24706@outpost.ds9a.nl> (raw)
In-Reply-To: <40BD6FDE.6090006@candelatech.com>
> You can check that they get to the wire in (almost?) all cases by watching
QoS settings may drop your packet before actually hitting the wire, but
after being enqueued to the kernel.
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2004-06-02 6:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 5:33 Select/Poll jyotiraditya
2004-06-02 5:54 ` Select/Poll David Schwartz
2004-06-02 6:12 ` Select/Poll Ben Greear
2004-06-02 6:38 ` bert hubert [this message]
2004-06-02 6:09 ` Select/Poll Ben Greear
2004-06-02 7:05 ` Select/Poll Vadim Lobanov
2004-06-02 14:11 ` Select/Poll Davide Libenzi
2004-06-02 15:28 ` Select/Poll khandelw
2004-06-03 15:10 ` Select/Poll Mike Jagdis
2004-06-03 15:53 ` Select/Poll khandelw
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=20040602063803.GA24706@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=davids@webmaster.com \
--cc=greearb@candelatech.com \
--cc=linux-kernel@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