[OpenAFS] Use of hyperthreading on AFS fileservers
Derrick Brashear
shadow@gmail.com
Mon, 22 Jul 2013 13:43:10 -0400
--001a11c20b94bd544804e21d3527
Content-Type: text/plain; charset=ISO-8859-1
The rx listener thread in a fileserver can float from thread to thread, but
even if it couldn't you don't necessarily get off: work for any given
client is not necessarily
handled all within a single thread, and thus not necessarily on a single
core. What this means is you get to incur context switches when one packet
is handled on the first
core and the next packet from the same client is on another core. So
there's no one "right" answer. And as long as but a single port (7000)
handles all traffic there is not a
convenient way to bind streamless (UDP) traffic from a single client to a
single core...
On Mon, Jul 22, 2013 at 1:21 PM, Rich Sudlow <rich@nd.edu> wrote:
> Are there any recommendations on why/why not to use hyperthreading on
> Intel machines used as fileservers with Red Hat 6.4 OS?
>
> Thanks,
>
> Rich
>
> --
> Rich Sudlow
> University of Notre Dame
> Center for Research Computing - Union Station
> 506 W. South St
> South Bend, In 46601
>
> (574) 631-7258 (office)
> (574) 807-1046 (cell)
> ______________________________**_________________
> OpenAFS-info mailing list
> OpenAFS-info@openafs.org
> https://lists.openafs.org/**mailman/listinfo/openafs-info<https://lists.openafs.org/mailman/listinfo/openafs-info>
>
>
--
Derrick
--001a11c20b94bd544804e21d3527
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div>The rx listener thread in a fileserver can float from=
thread to thread, but even if it couldn't you don't necessarily ge=
t off: work for any given client is not necessarily <br>handled all within =
a single thread, and thus not necessarily on a single core. What this means=
is you get to incur context switches when one packet is handled on the fir=
st<br>
core and the next packet from the same client is on another core. So there&=
#39;s no one "right" answer. And as long as but a single port (70=
00) handles all traffic there is not a<br></div><div>convenient way to bind=
streamless (UDP) traffic from a single client to a single core...<br>
</div></div><div class=3D"gmail_extra"><br><br><div class=3D"gmail_quote">O=
n Mon, Jul 22, 2013 at 1:21 PM, Rich Sudlow <span dir=3D"ltr"><<a href=
=3D"mailto:rich@nd.edu" target=3D"_blank">rich@nd.edu</a>></span> wrote:=
<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex">
Are there any recommendations on why/why not to use hyperthreading on<br>
Intel machines used as fileservers with Red Hat 6.4 OS?<br>
<br>
Thanks,<br>
<br>
Rich<br>
<br>
-- <br>
Rich Sudlow<br>
University of Notre Dame<br>
Center for Research Computing - Union Station<br>
506 W. South St<br>
South Bend, In 46601<br>
<br>
<a href=3D"tel:%28574%29%20631-7258" value=3D"+15746317258" target=3D"_blan=
k">(574) 631-7258</a>=A0(office)<br>
<a href=3D"tel:%28574%29%20807-1046" value=3D"+15748071046" target=3D"_blan=
k">(574) 807-1046</a>=A0(cell)<br>
______________________________<u></u>_________________<br>
OpenAFS-info mailing list<br>
<a href=3D"mailto:OpenAFS-info@openafs.org" target=3D"_blank">OpenAFS-info@=
openafs.org</a><br>
<a href=3D"https://lists.openafs.org/mailman/listinfo/openafs-info" target=
=3D"_blank">https://lists.openafs.org/<u></u>mailman/listinfo/openafs-info<=
/a><br>
<br>
</blockquote></div><br><br clear=3D"all"><br>-- <br>Derrick
</div>
--001a11c20b94bd544804e21d3527--