From: James Courtier-Dutton <James@superbug.co.uk>
To: "Paul G. Allen" <pgallen@gmail.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Linux Serial Performance
Date: Sun, 10 Jan 2010 19:42:34 +0000 [thread overview]
Message-ID: <4B4A2DAA.2050104@superbug.co.uk> (raw)
In-Reply-To: <bd8e30a41001091057t97f90abgffe9cca329ace477@mail.gmail.com>
On 09/01/10 18:57, Paul G. Allen wrote:
> I am wondering, have there been any performance tests comparing Linux
> serial IO to Windows and what was the result? Is it a problem in the
> comm API (e.g. - the Windows DLL having better performance than the
> Linux .so)? Is it a problem in the Linux serial driver itself? Is
> there something I can/need to do on Linux to tweak the driver and make
> it faster?
>
> Thanks,
>
> PGA
>
If you can narrow down the problem, one might be able to help.
I would suggest that you write a test Java program that both sends and
receives data on the same port and then post that source code to the list.
Anyone can then plug in a serial loopback connector, and reproduce the
problems you observe.
Without any way to reproduce the problems you observe, there is very
little chance of fixing it.
I suspect the problem is probably due to interrupts and serial buffer sizes.
As an aside, I would probably have used usb instead of serial as the
interface. It would be faster but not a lot more expensive.
Kind Regards
James
next prev parent reply other threads:[~2010-01-10 20:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 18:57 Linux Serial Performance Paul G. Allen
2010-01-09 19:10 ` Samuel Thibault
2010-01-09 19:32 ` Paul G. Allen
2010-01-09 19:46 ` Dr. David Alan Gilbert
2010-01-09 19:47 ` Michael Trimarchi
2010-01-09 20:30 ` Alan Cox
2010-01-09 23:51 ` Robert Hancock
2010-01-10 18:26 ` Krzysztof Halasa
2010-01-10 19:42 ` James Courtier-Dutton [this message]
2010-01-14 18:35 ` Paul G. Allen
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=4B4A2DAA.2050104@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pgallen@gmail.com \
/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.