From: gregkh@linuxfoundation.org (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: uart throughput
Date: Thu, 5 Apr 2018 21:19:53 +0200 [thread overview]
Message-ID: <20180405191953.GA19801@kroah.com> (raw)
In-Reply-To: <CAHhAz+io6_dS=+YO=Zd9rYuPomOOFtd2GsweKyvN1A4zKQZOVA@mail.gmail.com>
On Thu, Apr 05, 2018 at 10:08:14PM +0530, Muni Sekhar wrote:
> Hi All,
>
>
> I?ve an uart hardware implemented on Xilinx FPGA image and it connects
> to host CPU(Intel based chip) on PCIe bus in Linux platform.
>
>
> The following parameters were fixed or varied when measuring the UART
> throughput in internal loopback mode(UART_RX and UART_TX pins were
> internally connected):
>
>
> ? Uart baud rate
> ? Parity Bit
> ? Stop Bit(s)
>
>
> The primary factor affecting UART throughput is the baud rate, apart
> from this any other factors affect the UART throughput?
>
> For 4000000 bps uart baud rate, what should be the theoretical peak
> data throughput?
Um, you do know what "baud rate" means, right? And how stop bits and
parity are related to a baud rate?
Throughput all depends on a whole raft of different things. How exactly
have you measured this and where did you find any performance
bottlenecks?
thanks,
greg k-h
next prev parent reply other threads:[~2018-04-05 19:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-05 16:38 uart throughput Muni Sekhar
2018-04-05 19:19 ` Greg KH [this message]
2018-04-06 11:42 ` Alan Cox
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=20180405191953.GA19801@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).