Hi Anan,
You better use the same Grub kernel command line parameters both in 
run level 5 and in run level 3.
In order to be able to do so, keep the GRUB_CMDLINE_LINUX as what you had in 
init level 5, and assuming you are using one of the popular distros (like 
Fedora or recent Ubuntus), which runs systemd, the recommended way to what you 
call "disable the gui" is by a systemd command called systemctl.

So, when the gui mode is enabled, you will get:
systemctl get-default
graphical.target

And to disable the gui you can run:

sudo systemctl enable multi-user.target --force
sudo systemctl set-default multi-user.target

After boot, both in run level 3 and in run level 5, you will be able to verify 
that the kernel command line is as expected with:

cat /proc/cmdline

Regards,
Rami Rosen


-----Original Message-----
From: users [mailto:users-boun...@dpdk.org] On Behalf Of Anand Prasad
Sent: Tuesday, April 10, 2018 15:12
To: users@dpdk.org
Subject: [dpdk-users] Running DPDK application in Linux init level 3

Hi DPDK Team,
  I am trying to run DPDK application in Linux with init level 3 (no gui) and I 
am observing continuous packet drops on Rx side. But, If I boot Linux in init 
level 5 (GUI), then I dont see drops.
  I have provided linux command line arguments (for isolating the cpu cores and 
hugepates etc in "GRUB_CMDLINE_LINUX_DEFAULT" variable, and with those it's 
working fine in init level 5. But, not sureif these configuration are 
applicable when I boot in Init level 3?
 To boot in init level 3, I am setting GRUB_CMDLINE_LINUX="3" , is it correct? 
If not please suggest what is theother method.
Thanks in advance.Anand

Reply via email to