| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
| |
* Makefile.am, arpa/Makefile.am, machine/Makefile.am, net/Makefile.am,
netinet/Makefile.am, nfs/Makefile.am, rtems/Makefile.am,
rtems_servers/Makefile.am, rtems_webserver/Makefile.am,
sys/Makefile.am, vm/Makefile.am:
Apply include_*HEADERS instead of H_FILES.
* include/Makefile.am: Remove.
* Makefile.am: Add handling of *.h files.
* configure.in: Remove include/Makefile.
|
| |
|
|
|
|
|
| |
* kern/Makefile.am, lib/Makefile.am, libc/Makefile.am,
net/Makefile.am, netinet/Makefile.am, nfs/Makefile.am,
pppd/Makefile.am, rtems/Makefile.am, rtems_servers/Makefile.am,
rtems_webserver/Makefile.am, wrapup/Makefile.am: Include compile.am
|
| |
|
|
| |
* netinet/tcp_input.c: Spelling corrections.
|
| | |
|
| |
|
|
| |
adds .cvsignore.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that contains the automake files for libnetworking plus a couple of
minor fixes. [Now only one unused/unsupported Makefile.in remains
(./c/src/lib/libbsp/hppa1.1/pxfl/Makefile.in).]
To apply:
patch -p1 < rtems-rc-20000118-7.diff
/bin/sh rtems-rc-20000118-7.rm
/bin/sh rtems-rc-20000118-7.add
./bootstrap
Notes:
* I have tested this one by building all BSPs for m68k, powerpc, sh and
unix with toolchains built since last weekend.
* I did not touch libnetworking's directory layout.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
report from Philip A. Prindeville <philipp@zembu.com>:
I was working on a device driver for a certain ethernet chipset that
occassionally wraps in its buffer, and causes a resulting mbuf chain
with only a few dozen bytes in the first mbuf of the chain.
I wouldn't have thought this would be a problem, until I ran some
stress tests that flooded the ethernet receiver with packets and
started to get panics here:
250
251 if (m->m_pkthdr.len < sizeof(struct ip))
252 goto tooshort;
253
254 #ifdef DIAGNOSTIC
255 if (m->m_len < sizeof(struct ip))
256 panic("ipintr mbuf too short");
257 #endif
258
259 if (m->m_len < sizeof (struct ip) &&
260 (m = m_pullup(m, sizeof (struct ip))) == 0) {
261 ipstat.ips_toosmall++;
262 return;
263 }
264 ip = mtod(m, struct ip *);
and the panic was at line 256. But if I #undef'd DIAGNOSTICS,
then the m_pullup() at line 260 does the right thing and the packet
ends up being processed just fine.
So I started wondering, (a) why was the test checking for
something that apparently wasn't a fatal condition but rather
one that is subsequently recovered from a couple of lines later
and (b) why panic as a diagnostic "aid" from a recoverable
condition rather than just (say) log a message to the console?
All of this seems overly severe for no reason that is readily
apparent to me.
|
| | |
|
| |
|
|
| |
printing messages.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
prototype.
|
| | |
|
| |
|
|
| |
the inet checksum routine.
|
| |
|
|
|
|
|
|
|
|
|
| |
I've fixed a few minor probs with the optimised version that Eric put
together for me the other day and sent the fixes back to him. Provided he
doesn't have a problem with it we've got a pretty solid in_cksum for the
ColdFire as well as straight m68k. I've enclosed my updated in_cksum_m68k.c
At the moment my own bottlenecks are elsewhere...as my driver is pulling
16bit data chunks through a libchip-esq access routine from the chip which
for a polled I/O device is never going to be quick.
|
| |
|
|
| |
for the ColdFire.
|
| |
|
|
| |
file to switch out to CPU specific implementations.
|
| | |
|
| | |
|
| | |
|
| |
|
