arch
http://shopping.yahoo.com
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to
"[EMAIL PROTECTED]"
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Sem
he above. It deals
with a long-dead version of BSD, but the fundamentals have not changed
that much. In addition, the book is a very well-done code walkthrough
of the networking code in BSD (again, from long ago, but the "bones"
are good).
Regards,
Justin
--
Justin C. Walker, Curm
apple.com/darwin). The code is available under
Apple's open source license (APSL 2.0).
Regards,
Justin
--
/~\ The ASCII Justin C. Walker, Curmudgeon-at-Large
\ / Ribbon Campaign
X Help cure HTML Email
/ \
___
[EMAIL PROTECTED] mailing l
e type checking).
Cheers,
Justin
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics| If you're not confused,
| You
ierr();
return;
} else {
*sbp = sb2;
action = ADD_EVENTS;
}
}
}
.
.
}
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to
&qu
gement of Mac OS X systems.
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics| If you're not confused,
| You're not paying attention
*--*---
ng scheme (except for mbufs).
>> The implementation is polling. The implementation is pretty
>> light-weight.
>
> Where do the Darwin gdb sources live, so we can see the gdb end of it
> too? I've looked, but have so far been unable to find them.
>
ds on where they put it. If it depends on I/OKit then we
>> won't be able to use it easily I figure.
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics| When LuteFisk is outlawed
backtrace seems to have disappeared between the time you
> wrote the above and when you sent it.
>
> There are several USB components in the darwin repository; check them
> out and look at the code.
>
> Regards,
>
> Justin
>
> --
> Justin C. Walker, Curmudgeon-At-Lar
l open() from an ISR.
Finally, don't call tsleep() from an ISR.
Oh, and the backtrace seems to have disappeared between the time you
wrote the above and when you sent it.
There are several USB components in the darwin repository; check them
out and look at the code.
Regards,
Justin
--
Just
with the observed truncation of packets when read from a socket. 20.3
was what I intended, as it covers the observed behavior (at least,
that's my story, and I'm sticking with it :-]).
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large
ext or all data, but I admit my memory is almost gone, and I don't
> remember PDP/11 architecture all that well either.
You're correct; that's what I meant by the 'granularity' of the
hardware. You had to share a fairly hefty chunk of memory, so (except
sses for the purposes of sharing data. Given the granularity of
the PDP-11 "VM" hardware, it seemed like a bad tradeoff, and wasn't
considered useful until long after the PDP-11 went to the Boston
Computer Museum, where it sipped tea and complained about the Red Sox.
Regar
then perhaps it should be documented
> somewhere.
It is and it is :-}. At least, Stevens discusses it in "Unix Network
Programming", v1, 2e (sec. 20.3). Different systems, alas, treat this
case differently.
Regards,
Justin
--
Justin C. Walker, Curmu
was different.
> On Linux:
> -w1 crow crow0 Jan 16 10:32 /tmp/foobar
>
> On Tru64/FreeBSD:
> --1 crow users 0 Jan 16 10:30 /tmp/foobar
>
> I'm not sure what the result supposed to be. Any ideas ?
>
> Be
use this kind of OS. Its
kernel is monolithic, in that all the pieces live together in the same
address space, and communicate via procedure calls, not messages. Mach
messaging can be, and sometimes is, used between processes, and between
process and kernel [in some cases; BSD system calls are
On Wednesday, May 31, 2000, at 06:15 AM, Alain Jourez wrote:
> Hi there,
>
> I beleive the sticky bit was used historically to prevent a whole
> process to be swapped. What is the precise meaning of it ?
The 'sticky' bit was, historically, intended to keep an executable's swap
image around aft
livered to your system. A
"ps aux" will verify whether 'sendmail' is running.
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics |
Manager, CoreOS Networking| When crypto is outlawed,
Apple Computer, Inc.
> From: Jonathan Lemon <[EMAIL PROTECTED]>
> Date: Sat, 25 Mar 2000 13:35:53 -0600
> To: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Subject: Request for review (HW checksum patches)
> X-Mailer: Mutt 1.0pre2i
> Delivered-to: [EMAIL PROTECTED]
> X-Loop: FreeBSD.org
>
> I have a set of patches which al
closed. See the code, e.g.,
for netstat, or for ifconfig. There's also a sysctl() request that
works.
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics |
Manager, CoreOS Networking| Men are from Earth.
Apple Computer, Inc.
n;
> m->m_len += hlen;
> m->m_pkthdr.rcvif = (struct ifnet *)0;
>
> though I can't confirm this immediately. (And I can't see why
> this would have worked at all).
>
> Peter
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsu
The problem, I believe, is the cost of using multiple mbufs per
packet when a packet exceeds MHLEN but is less than MINCLSIZE.
Probably the best performance, at the expense of memory, is had by
setting MINCLSIZE=MHLEN.
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-L
ve 'ping' set its socket buffer sizes based
on the requested size
- use 'sysctl' to change the system's default send/receive buffer
sizes (see net.inet.raw.maxdgram, net.inet.raw.recvspace).
Naturally, I haven't tried this, or eyeballed the code, so treat
ays around this:
- change the code to have 'ping' set its socket buffer sizes based
on the requested size
- use 'sysctl' to change the system's default send/receive buffer
sizes (see net.inet.raw.maxdgram, net.inet.raw.recvspace).
Naturally, I haven't tri
alternative
for those that want to use it. Its use is intended to match that of
select(), so that developers don't have to restructure existing code
to use it.
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics |
Manager, CoreOS Networking
> From: Garance A Drosihn <[EMAIL PROTECTED]>
> Date: 1999-09-09 10:33:59 -0700
> To: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Subject: Re: message queues for I/O (usenix paper)
> In-reply-to: <[EMAIL PROTECTED]>
> X-Sender: [EMAIL PROTECTED]
>
> At 6:44 PM
vide a uniform mechanism for
fielding events from any subsystem. It will be made more interesting
by the need to incorporate mach message handling in addition to
file-descriptor-based events.
Have a look, should this be of interest. I'll be happy to field
questions, since the doc is
anism for
fielding events from any subsystem. It will be made more interesting
by the need to incorporate mach message handling in addition to
file-descriptor-based events.
Have a look, should this be of interest. I'll be happy to field
questions, since the doc is a bit, oh, scant.
are will remain valid.
In the meanwhile, there ought to be a simple version of this problem
that we can solve :-}. I think I'll get down off this soap box for
a bit...
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semant
rom that identity to who you are will remain valid.
In the meanwhile, there ought to be a simple version of this problem
that we can solve :-}. I think I'll get down off this soap box for
a bit...
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large *
Institute
n't go with IRS because we felt it was
> not flexible enough.
FWIW, it's also GPL'd, according to the web site.
j
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics |
Manager, CoreOS Networking| When crypto is outlawed,
king about.
>
> In NetBSD, we specifically didn't go with IRS because we felt it was
> not flexible enough.
FWIW, it's also GPL'd, according to the web site.
j
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics |
Manager, CoreOS Network
a change in port status,
as might happen if a driver reinitializes the link. The switches are
executing a spanning tree algorithm on the new port, looking for
loops. If the switches can be configured to not do this (only needed
for switch-switch connection), you might try that as well.
when there's a change in port status,
as might happen if a driver reinitializes the link. The switches are
executing a spanning tree algorithm on the new port, looking for
loops. If the switches can be configured to not do this (only needed
for switch-switch connection), you migh
ts
> ^^^
>
> What broke?
Out of curiosity, what does 'arp -a' show after the 'arp -s'
command? Could be something like the "alias" response of
'ifconfig'...
Regards,
Justin
--
Justin C. Walker, Curmudgeon
t: File exists
> ^^^
>
> What broke?
Out of curiosity, what does 'arp -a' show after the 'arp -s'
command? Could be something like the "alias" response of
'ifconfig'...
Regards,
Justin
--
Justin C. W
different kinds of events, including Mach messages (not a big deal
for this group, of course).
See www.publicsource.apple.com and follow the links to Darwin OS.
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics |
Manager, CoreOS Networking|
number of
different kinds of events, including Mach messages (not a big deal
for this group, of course).
See www.publicsource.apple.com and follow the links to Darwin OS.
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics |
Manager, CoreOS Networking
tence. How persistent do
you want it? I'd bet that no matter what source you use, there's
always the problem of "it broke; I had to replace it; now what?".
Kind of like your grandfather's axe, which has had six handles and
two blades over its lifetime, but it&
e: can't allocate llinfo for
> > 127.0.0.1rt
I'm not sure this is relevant, but the loopback address should
*not* be fed to ARP. That's attached to the loopback interface
(lo0), and shouldn't be seen on any wire. Could be your config is
seriously fouled up.
Regard
lurry.
Raw (character) disk devices have always had this behavior. Back in
The Good Old Days, physio() actually worked direct to user buffers,
so the rule was "block size and granularity", was dictated by a combo
of what physio() and the device driver were willing to do.
Regards,
der why you're always
in that routine when this occurs, but I can't provide any
illumination there. How frequently does this occur?
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics |
Manager, CoreOS Networking| When crypto is
lity for support of "other OSs
and their [unprintable] stacks" (this in response to the concern that
about more than one MAC address per IP address).
Being able to use this functionality may take a bit more
engineering, but it seems that there is good reason to consider it as
o tell the driver to go to
promiscuous mode to emulate this (an "I really want this" request?),
but I'm not sure it should be the default response to the "set
hardware address" request.
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for Gen
een transparently.
>
> I think you need to reconsider that idea. How are you going to double
> the bandwidth of the wire?
I think Dan's thinking of switched ethernet, with a high-speed
switch that can handle the bandwidth. Clearly won't work on thinnet,
but with 10BaseT,
't be changed.
DECNet, for example, assumes for some protocols at least, that the
MAC address is one from the block of addresses owned by DEC.
CompaqNet? Sheesh.
Regards,
Justin
--
Justin C. Walker, Curmudgeon-At-Large *
Institute for General Semantics |
Manager, CoreOS Network
46 matches
Mail list logo
